subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Mark Phippard <markp...@gmail.com>
Subject Re: "400 Bad Request" on commit with 1.7 client to 1.7 server
Date Fri, 02 Dec 2011 00:29:00 GMT
On Thu, Dec 1, 2011 at 5:34 PM, Aaron V. Humphrey
<aaron@investopedia.com> wrote:
> We recently set up a new SVN 1.7.1 server, using CollabNet Subversion Edge 2.1.
>  We seemed to be able to connect to it properly using TortoiseSVN 1.6 clients,
> and version 1.7 clients (both TortoiseSVN and Cygwin command-line) were able to
> use any command which did not try to update the repository.  However, trying to
> do a simple commit failed with the following error message:
>
> Server sent unexpected return value (400 Bad Request) in response to POST
> request for '/svn/<reposname>/!svn/me'
>
> In the access.log file on the server was the following line:
>
> 192.168.34.141 - <username> [01/Dec/2011:15:14:38 -0700] "POST
> /svn/<reposname>/!svn/me HTTP/1.1" 400 226
>
> which wasn't very helpful.  I turned up Apache logging on the server to
> "LogLevel debug" and got a lot of information, but nothing that seemed too
> helpful either.
>
> We are using https: to access to repository.  It does give a warning because I
> am using the default "svnedge.collab.net" server certificate, but I asked it to
> accept it permanently the first time.  Among the debug information it gives is
> "SSL negotation finished successfully", too.
>
> Based on a post from last week, I tried adding
>
> SVNAdvertiseV2Protocol off
>
> to my httpd.conf under <Location />, but it didn't seem to help.
>
> Let me know what other information I can provide to try to resolve this.

Subversion Edge does not have the location block for SVN in the
httpd.conf file.  Have you customized the configuration files beyond
this?  There is no reason you should have to add that directive
anyway.

Assuming you are using the default configuration that SVN Edge writes,
which I know works properly, have you defined any authz rules in the
"Access Rules" section of the Repositories tab?  If so, maybe
temporarily replace the rules with:

[/]
* = rw

And see if that solves anything.

-- 
Thanks

Mark Phippard
http://markphip.blogspot.com/

Mime
View raw message