Re: [squid-users] Odd "https" behaviour.

On Wed, 17 Mar 2004, Tim Neto wrote:

> --------------------------------------------------------------------------------------------------------------------------------------------------------------
> 1079532258.813 0 172.16.1.13 TCP_DENIED/407 1725 CONNECT
> www.komatsuamerica.net:443 - NONE/- text/html
> 1079532261.705 878 172.16.1.13 TCP_DENIED/403 1453 GET
> http://www.komatsuamerica.net/_mem_bin/applicationLogin.asp? - NONE/
> -text/html
> --------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Any ideas as to why Squid is changing the request from a "https" request
> to a non-secure "http" request.

Looking again at your data, and it very much looks like you are using a
broken browser which "forgets" to use https if authentication is required.

> We have several sites that are only secure sites that our users need to
> access. If the user first goes to a non-secure web site, access to the
> secure web site works.

Also makes sense given the above as the proxy authentication then gets
negotiated before the user tries to visit a https site, so the bug in the
browser is avoided.

Try using another browser and/or the latest security updates to your
browser.

Regards
Henrik
Received on Wed Mar 17 2004 - 18:49:29 MST