400 Bad Request -- proxy problem?

[Matthew Cahn <ma...@gmail.com>]

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:

PROXY_ENABLED="yes"
HTTP_PROXY="http://proxy-server.bms.com:8080"
FTP_PROXY="ftp://proxy-server.bms.com:8080"
GOPHER_PROXY=""
NO_PROXY="bms.com"

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

[helpers]
editor-cmd = emacs

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

[auto-props]
*.py = svn:eol-style=native
README.* = svn:eol-style=CRLF
*.TXT = svn:eol-style=CRLF


Thanks for any help,
Matthew

Re: 400 Bad Request -- proxy problem?

[Matthew Cahn <ma...@bms.com>]

I answered my own question.  In case anyone else falls over this, 
~/.subversion/servers needed to be set up so that requests to the 
outside are proxied, and requests to our internal repository are not.  
For example:

[global]

[groups]
bms = *.bms.com
other = *

[bms]

[other]
http-proxy-host = proxy-server
http-proxy-port = 8080



Matthew Cahn wrote:

> 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:
>
> PROXY_ENABLED="yes"
> HTTP_PROXY="http://proxy-server.bms.com:8080"
> FTP_PROXY=" ftp://proxy-server.bms.com:8080"
> GOPHER_PROXY=""
> NO_PROXY="bms.com <http://bms.com>"
>
> And my ~/.subversion/config:
> [global]
> http-proxy-host = ""
>
> [helpers]
> editor-cmd = emacs
>
> [miscellany]
> global-ignores = *.o *.lo *.la #*# .*.rej *.rej .*~ *~ .#* .DS_Store *.pyc
> enable-auto-props = yes
>
> [auto-props]
> *.py = svn:eol-style=native
> README.* = svn:eol-style=CRLF
> *.TXT = svn:eol-style=CRLF
>
>
> Thanks for any help,
> Matthew


-- 
--------------------------------
|  Matthew Cahn
|  Principal Systems Analyst
|  Bristol-Myers Squibb Company
|  Mailbox code: H23-05
|  P.O. Box 4000
|  Princeton, NJ 08543-4000
|
|  Phone: (609) 252-3477
|  Fax:   (609) 252-6030
|  Email: Matthew.Cahn@bms.com
|  Pager: matthew_cahn@imbta.com
--------------------------------