credentials dropped using svn
Brought to you by:
liteyear
Menu
▾
▴
#2 credentials dropped using svn
Try checking out a project through an authenticating proxy... the credentials are dropped.
svn: Server sent unexpected return value (407 Proxy Authentication Required) in response to PROPFIND request for '/svn/trunk'
fyi, you must setup your .subversion/servers file to point at authoxy. (first start with no login/pass defined to make it fail)
If you do set your proxy login/pass in the servers file, the request works, but it should be using the authoxy login/pass by default anyways.
I'm also having the same issue with an edge-build of Colloquy IRC that has a proxy support patch added... ping me if you want details on this as well.
confirmed this with a packet sniffer (wireshark)... in these rare cases, Authoxy is not sending the Proxy-Authorization header in the request to the upstream proxy.
svn co http://rubygems.rubyforge.org/svn/
Here is the sniffed outgoing packet content (no proxy-auth):
PROPFIND http://rubygems.rubyforge.org/svn HTTP/1.1
Host: rubygems.rubyforge.org
User-Agent: SVN/1.5.2 (r32768) neon/0.28.3
Connection: TE
TE: trailers
Content-Type: text/xml
Accept-Encoding: gzip
Depth: 0
DAV: http://subversion.tigris.org/xmlns/dav/svn/depth
DAV: http://subversion.tigris.org/xmlns/dav/svn/mergeinfo
DAV: http://subversion.tigris.org/xmlns/dav/svn/log-revprops
Content-Length: 300
Accept-Encoding: gzip
There are rare situations where a PROPFIND request wont trigger the header insertion. Perhaps SVN prompts these situations. A private dev build specifically addresses PROPFIND. Will investigate whether it fixes this issue and go from there.