Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-05 Thread Gustavo Chaves
On 5 dez, 09:13, Philip Martin wrote: > Your problem with POST requests is not yet understood.  It's might be > some overlap between Subversion directives in your apache config, or > between Subversion directives and non-Subversion directives.   Only you > can really identify the problem at presen

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-05 Thread Philip Martin
Gustavo Chaves writes: > However, I understand that by turning that option Off I'm telling > apache to use the old HTTP protocol, giving up on the new one that is > much more performant, right? Yes. > Regarding the 1.7.2 release, I understand that it should appear > shortly. However, what I get

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-05 Thread Gustavo Chaves
On 5 dez, 05:59, Konstantin Kolinko wrote: > 2011/12/4 Gustavo Chaves : > > There are known problems with handling of POST requests in 1.7.0 an 1.7.1. > > In 1.7.2 changes list that is mentioned as > * make mod_dav_svn ignore non-Subversion POST requests (r1187695) > > The POST request are from th

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-05 Thread Konstantin Kolinko
2011/12/4 Gustavo Chaves : > I straced the httpd daemon to try to get any hint. The last syscalls > before the error are these: > > 17748 read(18, "POST /admin/!svn/me HTTP/1.1\r\nUs"..., 8000) = 441 There are known problems with handling of POST requests in 1.7.0 an 1.7.1. In 1.7.2 changes list

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
Just one more information. I was using the packages CollabNetSubversion-extras and CollabNetSubversion-server version 1.7.0-2. I've just upgrade them to version 1.7.1-1 but the problems remain. -- Gustavo.

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
I straced the httpd daemon to try to get any hint. The last syscalls before the error are these: 17748 read(18, "POST /admin/!svn/me HTTP/1.1\r\nUs"..., 8000) = 441 17748 stat("/l/home1/svn/admin/htdocs/admin/!svn/me", 0x7fffce99c130) = -1 ENOENT (No such file or directory) 17748 lstat("/l", {st_m

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-04 Thread Gustavo Chaves
On 1 dez, 22:29, Mark Phippard wrote: > > 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 config

Re: "400 Bad Request" on commit with 1.7 client to 1.7 server

2011-12-01 Thread Mark Phippard
On Thu, Dec 1, 2011 at 5:34 PM, Aaron V. Humphrey 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 a