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 17:37:21 -0400
Message-ID: <3906C56A7BD1F54593344C05BD1374B107839249@SUS-MA1IT01>
To: "'Webdav WG'" <w3c-dist-auth@w3c.org>

There was not enough information in this message to determine
what exactly was the problem that he was reporting.  You can type
in a non-slash terminated URL into IE5 (e.g.
<http://www.webdav.org/deltav>, and relative references are
handled properly.

Perhaps he was testing against a poorly implemented server
(i.e. one that did not either 302-redirect to the slash terminated
or did not return a slash-terminated Content-Location header).


-----Original Message-----
From: Lisa Dusseault [mailto:lisa@xythos.com]
Sent: Tuesday, September 17, 2002 1:28 PM
To: 'Clemm, Geoff'; 'Webdav WG'
Subject: RE: Issue: Requiring server to use / terminated URL for
returned collections

I dug out another testimonial to the interoperability problems of not
consistently using trailing slashes. 

Geoff Alexander said:
"We are developing a WebDAV server and have encountered interoperability
problem with request on collections in which the resource does not have
trailing slash.  Where do things stand on this issue?  Our testing
that the above does not work in the real world.  For example, both IE 5
Netscape 4.7 do not properly process relative references in response to
GET request on a collection without the trailing slash..  I guess one
say that IE and Netscape only support the HTTP protocol and not WebDAV
protocol, but then our server would have to determine whether the
was HTTP or WebDAV (which is not a workable solution).  Also, we have
encountered interoperability problem with other WebDAV clients."


Received on Tuesday, 17 September 2002 18:20:24 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 20:01:26 UTC