Re: [squid-users] Forcing HTTPS

From: Sketch <[email protected]>
Date: Wed, 3 May 2006 11:47:17 -0400

On 5/3/06, Christoph Haas <email@christoph-haas.de> wrote:
> On Wed, May 03, 2006 at 07:23:12AM -0400, Sketch wrote:
> > Is there anyway to force https for certain URLs with squid?
> >
> > For example, http and https are on the same cache_peer and people
> > accessing the webpages, for example:
> >
> > http://site.com/user
> >
> > Should be able to use http *or* https, however accessing:
> >
> > http://site.com/admin
> >
> > should answer to http, but redirect to https, thus allowing only https.
>
> Isn't that something the site.com administrator should take care of? That's
> close to trivial with Apache for example.

The problem arises when squid is doing the SSL business and only talks
to the origin server in http. To the apache server, everything is
http, you can see how this would loop: Request -> https -> squid ->
http -> origin server -> http -> squid -> etc..

Can quid 2.5 be configured as a pass through for https, and leave the
ssl layer stuff to the origin server *without* using a redirector?
Received on Wed May 03 2006 - 09:47:18 MDT

This archive was generated by hypermail pre-2.1.9 : Thu Jun 01 2006 - 12:00:01 MDT