Recently our development subversion server was updated and my happy svn existence was interrupted by a mysterious lack of access and a smugly returned and vague response to svn commands:
svn: OPTIONS of 'http://svn.ourcompany.com/svn/integration/trunk': 200 OK (http://svn.ourcompany.com)
By adding the following lines to C:\\Documents & Settings\\{your-name}\\Application Data\\Subversion\servers file, I was able to fix the problem:
[global]
http-proxy-exceptions = svn.ourcompany.com
http-library=neon
#neon-debug-mask=138
My network connections exceptions (Control Panel//Internet Connections//Connections/LAN Settings//Advanced//Exceptions) was ignored by SVN.
By the way, that last line neon-debug-mask=138 was very helpful in getting to the root cause by displaying a trace of what SVN was doing while servicing my request. What also helped was Wireshark. Wireshark allows you to trace your network connections and filter message content based on source and destination addresses and protocol types.
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment