Re: [squid-users] Squid and OWA again

OWA needs to EITHER accept the requests using SSL, or see the custom
header added by the SSL frontend instructing OWA that there is a SSL
frontend.

Note that to do any of the two you need the SSL update (or hack Squid
to add the header), as standard Squid-2.5 does not support EITHER of
forwarding requests using SSL to the backend server or adding the
custom header telling OWA that there is a SSL frontend server taking
care of the SSL part..

Rewriting URLs in attempts to fool OWA does not work. For OWA to work
it needs to have a 100% clear understanding of which URL the client
is requesting, including which protocol the client is using (http or
https), hostname, the exact urlpath, everything.

Regards
Henrik

On Tuesday 10 December 2002 21.01, Adam Lewis wrote:
> Should I enable SSL on the OWA server first or can I just go SSL to
> squid and rewrite the header before it gets to the OWA server from
> https to http?
>
> Thanks,
>
> Adam
> ----- Original Message -----
> From: "Henrik Nordstrom" <hno@squid-cache.org>
> To: "Adam Lewis" <adamlewis@catt.com>
> Cc: "Squid Users" <squid-users@squid-cache.org>
> Sent: Monday, December 09, 2002 8:39 PM
> Subject: Re: [squid-users] Squid and OWA again
>
> > You will need the SSL update to Squid-2.5 for running Squid as an
> > SSL frontend to OWA, and Squid needs to be configured to use your
> > OWA server as a cache_peer.
> >
> > See http://devel.squid-cache.org/ssl/ for some information about
> > the changes included in the SSL update.
> >
> > Regards
> > Henrik
> >
> > On Tuesday 10 December 2002 02.12, Adam Lewis wrote:
> > > Thanks for all of your help. I now have it working. Don't
> > > have SSL working yet which will be another challenge I'm sure,
> > > but thanks again. Once I do get it working, I will compare it
> > > with other docs and make one of my own to contribute :)
> > >
> > > Adam
Received on Tue Dec 10 2002 - 16:12:15 MST