RE: Chaining of SSL proxies

Hi group

Thanks for all the hints, they worked just fine, and are repeated below.

Silly me for not reading the .conf files - I did check the FAQ and there
was nothing there. Looks like I need to blow myself a big fat
raspberry.

Duane's response regarding Javascript seems unnecessary for my site, in
light of the fact that our parent proxy (Netscape) is able to access
both our Intranet and the Internet through the firewall. However where
we don't want to bounce all the way across the Pacific and back, some
time in the future as our network evolves, it may be necessary to make
the switch.

For now we're running just fine.

Regards

Jason Armistead
armistej@oeca.otis.com

>----------
>From: David Luyer[SMTP:luyer@ucs.uwa.edu.au]
>Sent: Monday, 3 November 1997 19:55
>To: Armistead, Jason
>Subject: Re: Chaining of SSL proxies
>
>You can specify the SSL parent with something like ssl_proxy or ssl_parent;
>see squid.conf. As long as the netscape proxy can talk SSL...
>
>David.

----------------------------------------

>Have you tried the ssl_proxy config variable? Point this at the proxy
>nearest the firewall. If this proxy can't see your intranet, you'll need
>a PAC script that says go direct for internal hosts.
>
>Ian Redfern (redferni@logica.com)

-------------------------------------------

Squid currently has poor support for routing SSL requests. You might
not be able to make Squid forward the request as you need without
hacking the source code.

Your best bet would probably be Javascript...

Duane W.
Received on Mon Nov 03 1997 - 15:17:47 MST