Re: [squid-users] reverse proxying https

From: Richard Patterson <[email protected]>
Date: Thu, 13 Jul 2006 14:15:05 +1200

Merton Campbell Crockett wrote:
>
> On 12 Jul 2006, at 24:56 , Richard Patterson wrote:
>
>> I've got squid sitting acting as a reverse proxy (http_accel) like this.
>>
>> client -----https----> squid ----http----> web_server
>>
>> This is all fine and well, however, the web_server is returning urls
>> with "http://" hardcoded back to the client.
>>
>>
>
> I needed to provide this capability to a customer in 1998. The
> solution to the problem was to use split DNS, Apache, virtual hosts,
> and mod_rewrite. The internal web server was never "visible" to the
> Internet and with mod_rewrite the content didn't need to be on a
> single server. The one other advantage of this approach was that I
> could use mod_rewrite to address probes for vulnerabilities.
>
>
Hrm, bugger.

Apache was slow and sluggish in this application, and had its own set of
issues.

Anyone have any other ideas with squid? or know of any reason why a
simple redirector with s@http://@302:https://@
won't work?

-Richard
Received on Wed Jul 12 2006 - 20:15:11 MDT

This archive was generated by hypermail pre-2.1.9 : Tue Aug 01 2006 - 12:00:01 MDT