There are no browser settings - we are using transparent mode.
Will try with netscape on a Linux machine.
Would it seem right that the cache lookup is timing out for the HTTPS
-----Original Message-----
From: Henrik Nordstrom [mailto:hno@squid-cache.org]=20
Sent: Sunday, February 01, 2004 10:03 AM
To: Pat Emerick
Cc: squid-users@squid-cache.org
Subject: RE: [squid-users] Transparent HTTP changes to HTTPS

On Sat, 31 Jan 2004, Pat Emerick wrote:

> Marking packets is done by IPTables
> All port 80 traffic is sent to the proxy with a mark on it.
> Failure is observed when a user attempts to purchase online. Session=20
> starts at HTTP site then gets redirected on that site to an HTTPS url
> After a time the session fails - "Cannot not find server or DNS error"
> So, session is established and allowed then, in same session the port=20
> changes to 443. When this happens the session fails.
> Some times the user can refresh and/or go "back" then "forward" and=20
> the connection is restored.
> It feels like a cache problem? But not always.

Smells like a browser problem to me.

have you tried with another browser brand?

It can also be the web site which dislikes the IP address changing in
middlle of the session, but then retrying usually does not help.