RE: [squid-users] HTTPD reverse proxy

Matus,
The problem is that i have one public ip adress and several https servers.
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.
So do I have to understand that it's not possible to use squid in reverse
proxy mode with multiple https internal server ?

Best regards
 

> -----Message d'origine-----
> De : Matus UHLAR - fantomas [mailto:uhlar@fantomas.sk]
> Envoyé : mercredi 12 octobre 2005 09:16
> À : squid-users@squid-cache.org
> Objet : Re: [squid-users] HTTPD reverse proxy
>
> On 12.10 08:51, M Harrata wrote:
> > For my main problem wich is a bad request from squid to the internal
> Host
> > >
> > > In the squid log: access.log:
> > > 127.0.0.1 TCP_MISS/600 974 GET http://localhost:443/ -
> DIRECT/192.168.1.3
> > >
> >
> > Why squid is forwarding an http request while my client send https
> request ?
>
> that is the standard behaviour when using squid as reverse https
> proxy/accelerator - the acceleration means that http servers don't need to
> mess up with ssl - it's left on squid.
>
> squid-2.5 also can't connect using ssl without ssl patch (it only can
> accept
> ssl connections).
>
> There's no reason for squid to forward request as https, unless the
> network
> between squid and server is untrusted. But in such case, there's usually
> no
> need for using squid.
>
> --
> Matus UHLAR - fantomas, uhlar@fantomas.sk ; 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.
> Eagles may soar, but weasels don't get sucked into jet engines.
Received on Wed Oct 12 2005 - 03:26:28 MDT