> There is a difference between http://example.com/foo and
> http://example.com/foo/.
> The former refers to the actual directory entry, and the latter refers
> to the
> contents of the directory entry.
No, they are both URIs. There is no such thing as a directory. There
are
such things as collections, and the latter URI is a collection, whereas
the URI without a slash is not. Apache's filesystem does not allow two
different URIs to access the collection because they differ in
hierarchy,
which will result in client failure if any later response contains
relative URIs.
The server must send a redirect. Clients that do not receive a redirect
(because a published version is broken) are not really helped by not
receiving the redirect -- in fact, it causes them to be substantially
slower and buggy in later requests. That is why we default to sending
a redirect, and no this has nothing to do with the GET method.
Our responsibility is to encourage client developers to find a clue
and implement HTTP correctly. We only provide workarounds when they
are absolutely necessary for deployed applications, and even then only
when they are limited to that application's version.
....Roy
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Jan 14 12:25:17 2003