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

400 Bad Request -- proxy problem?

From: Matthew Cahn <matthew.cahn_at_gmail.com>
Date: 2007-03-02 22:52:11 CET

I'm attempting to use Subversion for the first time with our internal
Subversion server. I can do checkout, status, and update, but when I commit
I get:

svn: Commit failed (details follow):
svn: MKACTIVITY of '/svn/esn/!svn/act/5f7ed279-b82a-0410-b2a0-bb1b2937d13d':
400 Bad Request (http://discoverysvn.pri.bms.com)

This is from a SuSE 9 linux system. svn is 1.4.3. On another similar SuSE
box, 1.2.1 gives the same behavior. However, from Cygwin under Windows (v.
1.3.2) everything works. The server is 1.4.0.

In the server logs it appears that Cygwin/Windows is talking directly to the
server, but the SuSE boxes are going through our proxy server. Could anyone
give me a pointer to how to get svn under SuSE Linux to stop going through
the proxy server?

Here's my /etc/sysconfig/proxy:


And my ~/.subversion/config:
http-proxy-host = ""

editor-cmd = emacs

global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store *.pyc
enable-auto-props = yes

*.py = svn:eol-style=native
README.* = svn:eol-style=CRLF
*.TXT = svn:eol-style=CRLF

Thanks for any help,
Received on Sat Mar 3 05:00:28 2007

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.