You need a TCP relay such as plug-gw from TIS toolkit or a similar tool. SSL proxying in Squid is only for proxying, not rewerse-proxying. If you are not interested in acceleration of the origin server then using a TCP relay is probably more suitable for the HTTP part as well. Squid may be a over-kill application for your use. --- Henrik Nordstrom Spare time Squid hacker Murray Bathgate wrote: > > Henrik, > I have seen a number of posts on the newsgroups by yourself regarding > the utilisation of squid . I would be most grateful if you could help > with the following scenario . > > We have a internal webserver (IIS) running on our intranet that we wish > to allow limited access to from the internet . Currently we are > deploying SQUID on the inside partition of a VirtualVault firewall (HP), > and this proxies to the server . This works fine for HTTP but fails for > HTTPS . For the latter we are unsure if it is a configuration issue or > if Squid just doesnt support this type of proxying . > As it is internet users we cannot specify the changing of the proxy > settings in there browsers (we know this works). > We wish to however secure the transmissions with SSL (Actually 128bit > SGC) > > Thanks in advance > > Any input much appreciated > > Regards > Murray Bathgate > Wellington > New Zealand > [EMAIL PROTECTED]
