subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stefan Sperling <s...@elego.de>
Subject Re: 200 OK error on update with files that contain non-alphanumeric characters
Date Fri, 19 Oct 2012 13:53:14 GMT
On Fri, Oct 19, 2012 at 03:15:36PM +0200, Gautier DI FOLCO wrote:
> Hi all,
> 
> I have a quite annoying problem, I use svn 1.6.15 with mod_dav on Apache
> HTTPd 2.2.8 on the server side and sevral clients.
> 
> On the client side, when I add and commit a file which has spaces or
> non-ASCII
> characters, all works, but, if I try do do an update, I have the following
> error:
> Updating '.':
> svn: E175002: REPORT of '/svn/!svn/vcc/default': 200 OK (https://serve)

This 200 OK error is always bogus and a 1.6.x bug. It doesn't tell
anyone anything so you're unlikely to get help based on this
information.

The real error message is hidden within the server response body which
probably fails to parse because of invalid XML or something similar.
Are you able to reproduce the error with a 1.7 client?

Is any error logged on the server?

Note that 1.6.15 was released in November 2010, so you're missing out
on almost 2 years worth of bug fixes. The problem might already have
been fixed. Are you able to try to reproduce the problem with a more
recent release of Subversion on the server?
 
> I try to checkout my repository in an other folder, then update works well,
> but all the filename are urlencoded.
> 
> Is their a way to handle non-ASCII characters and espace in filenames or
> a way to be less annoying?
> 
> For your help,
> Thanks by advance.

Mime
View raw message