Re: URI reference to a directory

Am Donnerstag, 28.08.03, um 15:20 Uhr (Europe/Berlin) schrieb Israel 
Viente:

> Thanks for the answers. That clears the issue for file URL.
>
> But even in http, if I have "http://a/b/c/g/" it can result in getting
> "http://a/b/c/g/default.html"
> and "http://a/b/c/g" can result in getting "http://a/b/c/g" (g file).

Yes. In HTTP (GET) there are no folders, only resources.

//Stefan

> ----- Original Message -----
> From: "Stefan Eissing" <stefan.eissing@greenbytes.de>
> To: "Daniel Brockman" <daniel@brockman.nu>
> Cc: "Israel Viente" <israel_viente@il.vio.com>; <uri@w3.org>
> Sent: Thursday, August 28, 2003 9:02 AM
> Subject: Re: URI reference to a directory
>
>
>>
>>
>> Am Mittwoch, 27.08.03, um 21:40 Uhr (Europe/Berlin) schrieb Daniel
>> Brockman:
>>
>>>
>>> Israel Viente wrote:
>>>> Can a URI reference to a folder and not a file ?
>>>> How can you distinguish between a file URI and a folder one ?
>>>
>>> As I understand it, any URL ending with a slash identifies a 
>>> directory,
>>> while any other identifies either a file or a directory.
>>
>> That would be true for file: URIs. For other URI schemes you generally
>> cannot deduce such a thing. Pure HTTP does not have the concept of
>> a "file" or "directory". A client makes a GET on the URI and will
>> get a representation (or 404 or something else).
>>
>> WebDAV, as extension of HTTP, defines "collections" which behave
>> like folders in a file system. A client performs a PROPFIND request
>> and asks the server for the type of the resource.
>>
>> //Stefan
>>
>>
>>

Received on Thursday, 28 August 2003 08:42:27 UTC