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

Re: (Client) <--> (https proxy) <--> (https svn)

From: Joe Orton <joe_at_manyfish.co.uk>
Date: 2003-09-25 11:09:31 CEST

On Wed, Sep 24, 2003 at 09:59:38AM +0200, Patrick.LOGE@cec.eu.int wrote:
> (Client) <--> (https proxy) <--> (https svn)
> Does anybody use this architecture ?
> I can browse my repositories without problem with mozilla but if I try à
> checkout I get :
> D:\Temp\crotte>svn co https://xxx.yyyy.com/svn/svn_test
> Error validating server certificate: Unknown certificate issuer, Hostname
> mismatch. Accept? (y/N): y
> svn: RA layer request failed
> svn: PROPFIND request failed on '/svn/svn_test'
> svn: PROPFIND of '/svn/svn_test': Could not read response body: Secure
> connection truncated (https://xxx.yyyy.com)

This means that the server (or proxy) has closed the TCP connection
without first cleanly shutting down the SSL layer (or so neon claims).

I can check out from https://svn.collab.net/ via a 2.0.46 proxy OK from
a Linux client - can you enable neon debugging and get a debug trace?
You need to set neon-debug-mask to 259 in the global config section.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 25 11:28:29 2003

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.