Re: [squid-users] HTTPS & Reverse proxy

Oh. I was understanding it as:

client -- (https) --> Squid --- (https) ---> origin server

That Squid would be in between a client and a website that was using SSL.

So by making squid the endpoint, you can have all your webservers that are
behind it basically as HTTPS without actually having to configure the
webservers to do it? Squid would sort of be a "SSL abstraction", per se?

Adam Lang
Systems Engineer
Rutgers Casualty Insurance Company
http://www.rutgersinsurance.com
----- Original Message -----
From: "Henrik Nordstrom" <hno@hem.passagen.se>
To: "Adam Lang" <aalang@rutgersinsurance.com>
Cc: "Squid Users" <squid-users@squid-cache.org>
Sent: Monday, April 16, 2001 10:09 AM
Subject: Re: [squid-users] HTTPS & Reverse proxy

> It will accelerate it allright.
>
> With an SSL enabled Squid accelerator it looks like:
>
> client -- (https) --> Squid --- (http) ---> origin server.
>
> SSL is only used between the client and Squid. Between Squid and the
> origin server plain old HTTP is used without encryption. Squid acts as
> the SSL endpoint for the request.
>
> No, this does not apply to "transparent proxies", only accelerator
> setups where the accelerator can be seen as part of the origin server
> setup/environment.
>
> --
> Henrik Nordstrom
> Squid Hacker
Received on Mon Apr 16 2001 - 08:22:13 MDT