[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: "Unable to PUT new contents" - problem with Apache 2.2.25

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: Fri, 30 Aug 2013 09:49:28 +0100 (BST)

Hi Roderich.  Google("Apache 2.2.25 double encoding bug") -> it's a bug in httpd 2.2.25: <https://issues.apache.org/bugzilla/show_bug.cgi?id=55397>.  Ben Reser reported it so hopefully he can tell you any news regarding a fix, but downgrading to 2.2.24 for now would appear to be a good work-around.

- Julian

Roderich Schupp wrote:
> we recently upgraded our servers to Apache 2.2.25 and Subversion 1.7.11.
> Since then several of our users have problems commiting files with blanks
> somewhere in the pathname.


> Note that the URL in the PUT request looks like it has been URL-encoded
> twice ("...%20..." in the CHECKOUT URL got turned into "...%2520...").


> I downgraded the server to Apache 2.2.24 and the problem went away.
> I traced the actual TCP conversation in one of this cases and the double
> URL encoding seen is caused by the server: it sends the double encoded
> URL in the Location header of its response to the CHECKOUT request.
Received on 2013-08-30 10:50:23 CEST

This is an archived mail posted to the Subversion Dev mailing list.