[ee122] [Proj1b] index.html Question

[Jonathan D. Ellithorpe]

There's also the question of, what if index.html doesn't have the 
permissions your need (silly, I know), but the directory in which it 
resides does have proper permissions...

In this case, would we return Forbidden or the contents of the readable 
directory?

More concretely:

foo = haha/zip/bang/

So we jump to step 2:
Step 2: try opening foo + index.html
 - if get access error, move on to step 3 (?)
Step 3: try opening foo
 - if get access error, tell client forbidden
 - else return contents of directory

Thanks!
Jonathan


Lisa Fowler wrote:
> HTTP/1.0 403 Forbidden: /foo  Would be sufficient.  That was the
> request that the user made, and perhaps revealing that "/foo" was
> translated to "/foo/index.html" might be revealing too much about your
> system....
>
> -Lisa
>
> On 10/26/07, Allen Lee <leeallen at berkeley.edu> wrote:
>   
>> I have a question about what to print if we don't have read permission after
>> appending /index.html to the URI.  Suppose the server receives the request
>> "GET /foo HTTP/1.0" and successfully resolves the request by appending
>> /index.html to the URI.  If we don't have read permission for this file,
>> should the response be
>>
>> HTTP/1.0 403 Forbidden: /foo
>>
>> or
>>
>> HTTP/1.0 403 Forbidden: /foo/index.html
>>
>> Thanks,
>> Allen
>>
>> _______________________________________________
>> ee122 mailing list
>> ee122 at mailman.ICSI.Berkeley.EDU
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/ee122
>>
>>
>>     
> _______________________________________________
> ee122 mailing list
> ee122 at mailman.ICSI.Berkeley.EDU
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/ee122
>
>