Hi Henrik,
yes this is correct that there is nothing to cache on https, I know this but
my problem
is that the proxy authorisation on ssl connections does not work on M$
Browsers < IE6 ;o(
The Browsers crash if there was no authorisation over a http session first.
So I search for a way to do this with a trick (upstream for auth).
Regards Daniel
Server Environment for my ssl tests:
OS: Win32 NT4-XP
Squid: SquidNT 2.3 - 2.6
----- Original Message -----
From: "Henrik Nordstrom" <hno@squid-cache.org>
To: "Mr. Proxy" <Proxy4NT@gmx.de>
Cc: <squid-users@squid-cache.org>
Sent: Friday, June 13, 2003 2:40 PM
Subject: Re: [squid-users] cache_peer for authorisation on upstream proxy
> fre 2003-06-13 klockan 12.54 skrev Mr. Proxy:
>
> > On Squid:
> > squid.conf
> > cache_peer [IPProxy for Auth] parent 8080 7 no-query no-digest
> > no-netdb-exchange default login=PASS
> >
> > Is it correct that this only works for http and not for https?
>
> If works just as fine for https, but you will need to tell Squid that it
> is inside a firewall, or else it won't use peers for https as there is
> no benefit in caching (proxied https traffic is always uncacheable).
>
> Regards
> Henrik
--- snip ---
Received on Wed Jun 25 2003 - 06:15:45 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 17:17:38 MST