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

It seems related to my apache proxy config.
Sorry if it's the wrong place to post.

Let's say :

(X) Client
 |
 |
ISP
 |
 |_ISP's Router Masquarading on 192.168.2.10
    |
    |_ (A) Apache Proxy (192.168.2.10)
    |
    |_ (B) Http + SVN(192.168.2.112)
    |
    |_ (C) My Laptop
 
If I try [svn co https://192.168.2.112/svn/svn_test] from inside (C for ex)
it works.

But it doesn't work with the fully qualified name
https://xxx.yyyy.com/svn/svn_test
I tried from (A)(B)(C) and (X) always with the same error. (But a simple
browser works)

In fact, what I'm trying to do is an SSL tunneling using (A).

For now, (A) and (B) have their own self-signed certificat.

It's seems ok for a browser but Subversion doesn't seem to like it.

-----Original Message-----
From: Ben Collins-Sussman [mailto:sussman@collab.net]
Sent: mercredi 24 septembre 2003 15:00
To: LOGE Patrick (SANCO)
Cc: users@subversion.tigris.org
Subject: Re: (Client) <--> (https proxy) <--> (https svn)

Patrick.LOGE@cec.eu.int writes:

> svn: PROPFIND of '/svn/svn_test': Could not read response body: Secure
> connection truncated (https://xxx.yyyy.com)

I've never seen an error like this before.... ?

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 24 15:36:46 2003