[squid-users] Front-end-https: on header - not there

From: Alex Zlaten <[email protected]>
Date: Fri, 11 Jun 2004 09:01:35 -0500

Hi all,

I have Squid3 as ssl front-end for OWA 2000.
I can authenticate with the exchange server then my browser says I have
mixed secure/nonsecure information.

I view source and see that the exchange framed page is writing HTTP URLs
and I have front-end-https=on in the cach_peer tag.
So I sniffed out the header and I don't see the header entry being
transmitted by Squid.
Do I need to compile with other options for squid to pass this tag?

Here is the header from squid to exchange:

GET /exchange/ HTTP/1.0
Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
Accept-Language: en-us
Accept-Encoding: gzip, deflate
User-Agent: Mozilla/4.0 (compatible; MSIE 5.5; Windows NT 5.0; Installed
by Symantec Package)
Host: exchange.domain.com
Accept-Language: en-us
Accept-Encoding: gzip, deflate Authorization:
Basic xxxxxxxxxxxxxxxxxxxx
Via: 1.1 squid.domain.com (squid/3.0-PRE3)
X-Forwarded-For: xx.xx.xx.xx [client]
Cache-Control: max-age=259200 Connection: keep-alive

Thanks,
-Alex
Received on Fri Jun 11 2004 - 08:01:31 MDT

This archive was generated by hypermail pre-2.1.9 : Thu Jul 01 2004 - 12:00:02 MDT