Matus, thank you for your interest.
Theoretically, you've right, but I have no choice: the https servers are
historically here before me. I can't change all the architecture now.
Of course I'm using ssl patch for squid-2.5
What's working now ?
Client: https://squidServer-->SQUID2.5with-sslpatch--> http://internalServer
What is NOT working:
Client:https://squidServ-->SQUID2.5-With-sslPatch-->https://internalServer
Perhaps, there's no solution with squid ?
> -----Message d'origine-----
> De�: Matus UHLAR - fantomas [mailto:uhlar@fantomas.sk]
> Envoy�: mercredi 12 octobre 2005 12:32
> ��: squid-users@squid-cache.org
> Objet�: Re: [squid-users] HTTPD reverse proxy
>
> On 12.10 11:27, M Harrata wrote:
> > The problem is that i have one public ip adress and several https
> servers.
>
> do you need the connection between proxy and http servers encrypted? why?
>
> > That's why I want to use squid in reverse proxy mode. I had try with
> Apache
> > with the mod_proxy, mod_rewrite, and others mod_proxy_html modules, but
> I
> > wasn't satisfied.
>
> I'm not sure (I doubt) if apache's mod_proxy supports ssl client
> connections.
>
> > So do I have to understand that it's not possible to use squid in
> reverse
> > proxy mode with multiple https internal server ?
>
> as I already said, you need ssl patch for squid-2.5 or use squid-3.0
> the main question still remains, WHY? isn't http just enough? It should
> be,
> because you already descripted that, unless you don't trust the network
> between squid and https servers
> --
> Matus UHLAR - fantomas, [email protected] ; http://www.fantomas.sk/
> Warning: I wish NOT to receive e-mail advertising to this address.
> Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
> Spam = (S)tupid (P)eople's (A)dvertising (M)ethod
Received on Wed Oct 12 2005 - 05:35:27 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Nov 01 2005 - 12:00:04 MST