Thanks Anthony. In short, both. the scenario is we have multiple web servers on the intranet that we need to make available from the internet for roaming salespeople. What I'm looking to do is have squid act as a web proxy so that the salespeople can hit https://sqid.somewhere.com and be able to get to the intranet servers. I'm thinking something along the lines of //squid.x.com/server1 gets proxied to server1.intranet.com, //squid.x.com/server2 gets proxied to server2.intranet.com, etc.
does that make sense? thanks -----Original Message----- From: Antony Stone [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2003 4:10 PM To: '[EMAIL PROTECTED]' Subject: Re: [squid-users] reverse ssl-proxy? On Tuesday 18 November 2003 7:42 pm, John Hally wrote: > Hello Everyone, > > Is it possible to use squid as a reverse proxy to give access to intranet > servers from remote clients? Yes. http://www.squid-cache.org/Doc/FAQ/FAQ-20.html > What I'd like to do is have clients use SSL from their browsers and hit a > single host, which would then allow them access to intranet web resources. > Kind of a poor-mans VPN. Has anyone attempted something similiar? What are you trying to achieve here? Restricted access to intranet resources? (In which case, where/how are you authenticating people?) Confidentiality across the Internet? (In which case, why not just use simple HTTPS direct from client to server?) Antony. -- It suddenly dawns on the observer that there is no end to the creativity that these mindless hackers can come up with. - Kevin Kelly, Out of Control Please reply to the list; please don't CC me.
