W3C home > Mailing lists > Public > w3c-dist-auth@w3.org > July to September 2002

RE: Issue: Requiring server to use / terminated URL for returned collections

From: Clemm, Geoff <gclemm@rational.com>
Date: Tue, 17 Sep 2002 11:49:49 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B10841D60F@SUS-MA1IT01>
To: "'Webdav WG'" <w3c-dist-auth@w3c.org>

Good question, Julian.

I was going to respond "so that client side relative URL
processing is correct".  But of course, a better
way to handle that would be for the GET to just return the
slash-terminated name (or even better, the resource that it
is really redirecting the request to, such as "index.html")
in the Content-Location field, since the client is required
to use the value in the Content-Location field as the base
for relative URL processing.

So a 302 redirect is not even required for GET processing
(i.e. the server can just automatically forward the request
without an extra roundtrip for the 302 redirect).

Cheers,
Geoff

-----Original Message-----
From: Julian Reschke [mailto:julian.reschke@gmx.de]
Sent: Tuesday, September 17, 2002 10:24 AM
To: Clemm, Geoff; 'Webdav WG'
Subject: RE: Issue: Requiring server to use / terminated URL for
returned collections



Like Geoff said,

except:

> As indicated above, the 302 redirect is only required for a GET, and
> WebDAV clients commonly use PROPFIND and not GET to retrieve the state
> of a collection.

Where does this distinction come from?

I really don't want to get into a situation where 1) HEAD and 2)
PROPFIND/depth 0 say different things about the same resource.

Julian

--
<green/>bytes GmbH -- http://www.greenbytes.de -- tel:+492512807760
Received on Tuesday, 17 September 2002 11:50:22 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:44:01 GMT