W3C home > Mailing lists > Public > uri@w3.org > August 2003

RE: URI reference to a directory

From: Julian Reschke <julian.reschke@greenbytes.de>
Date: Thu, 28 Aug 2003 17:52:08 +0200
To: "Daniel Brockman" <daniel@brockman.nu>, "Israel Viente" <israel_viente@il.vio.com>, "Stefan Eissing" <stefan.eissing@greenbytes.de>
Cc: <uri@w3.org>
Message-ID: <JIEGINCHMLABHJBIGKBCAEOIIEAA.julian.reschke@greenbytes.de>

> From: uri-request@w3.org [mailto:uri-request@w3.org]On Behalf Of Daniel
> Brockman
> Sent: Thursday, August 28, 2003 5:46 PM
> To: Israel Viente; Stefan Eissing
> Cc: uri@w3.org
> Subject: Re: URI reference to a directory
>
>
>
> "Stefan Eissing" <stefan.eissing@greenbytes.de> wrote:
> >
> > 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.
> >
>
> So does http://a/b identify the same resource as http://a/b/, and, if it
> doesn't, what is the semantical difference?

a) not necessarily, and
b) whatever the server likes.

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Thursday, 28 August 2003 11:52:21 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Thursday, 13 January 2011 12:15:32 GMT