Re: [PATCH] mod_dav_svn directory listing i18n fix, and odd bug

cmpilato@collab.net writes:

> There are known bugs (well, known to me at least) in the mod_dav_svn
> code with respected to non URI-safe characters. The biggest one
> involves a XML element returned to the client in a PROPFIND called
> "baseline-relative-path". mod_dav_svn is NOT called
> svn_path_uri_encode() on that value, and that causes the client to try
> to lookup some URLs with non URI-safe characters.
>
> At this point, I don't know what to change -- that is, the item is
> called a "relative path", so should it remain un-encoded and client
> encode it when treating it as a URL, or should it be encoded and the
> client do nothing special to it?

I realized I could scout around in the access log for more
information, and found this:

127.0.0.1 - - [22/Jul/2002:19:57:35 +0200] "GET /svn/repos/!svn/ver/3h%C3%A4lsning HTTP/1.1" 500 240

Well, I should think that's a 500, since there's a slash missing
between the version number and the path name. How can this happen?
The fetch of revision 2 worked fine:

127.0.0.1 - - [22/Jul/2002:19:57:35 +0200] "GET /svn/repos/!svn/bc/2/h%C3%A4lsning HTTP/1.1" 200 6

Hm. One of them says "ver", the other says "bc". Maybe this means
something?

  // Marcus

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Jul 22 20:04:36 2002