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

Re: SVN Port 80 problem

From: Mike Mason <mgm_at_thoughtworks.net>
Date: 2004-01-30 15:21:23 CET

Colin Goudie wrote:

> However, going to work I found that we block outgoing SSL connections
> so I must use plane port 80 SVN.
> So I went home, commented out SSLRequireSSL from the Location section
> in subversion.conf and now I can't check out from my windows machine.
> It is saying REPORT request failed on '/svn/repos/hogs/!svn/vcc/default'
> REPORT of '/svn/repos/hogs/!svn/vcc/default': 400 Bad
> Request (http://my.dns.name.net <http://my.dns.name.net/>)
Subversion uses a number of HTTP protocol requests (other than simple
GET and POST) that the proxy at work might not be allowing through --
when you connect on port 80 do you get a real connection straight out,
or a proxied connection?

It should be possible to run Apache on a different port, just add the
relevant bind directive.

Alternatively you could try svnserve -- it requires a lot less
configuration and can work on any port. Finally, if you can get out on
port 22 you might try using svn+ssh to connect to your repository, but
beware about multi-user permissions issues.

Best regards,
Received on Fri Jan 30 15:23:52 2004

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.