RE: [squid-users] Squid & SSL on Windows

I restarted the service and see this now, which is mind boggling, because it
did not work prior, nor did it output anything in the access log.

1143568300.515 47 xxx.xxx.xxx.xxx TCP_MISS/302 1044 GET
http://sub.domain.tld/index.jsp - DIRECT/xxx.xxx.xxx.xxx text/html
1143568300.593 31 xxx.xxx.xxx.xxx TCP_MISS/302 1113 GET
http://sub.domain.tld/index.jsp - DIRECT/xxx.xxx.xxx.xxx text/html
1143568300.890 250 xxx.xxx.xxx.xxx TCP_MISS/200 2008 CONNECT
sub.domain.tld:443- DIRECT/xxx.xxx.xxx.xxx -
1143568301.562 281 xxx.xxx.xxx.xxx TCP_MISS/200 7874 CONNECT
sub.domain.tld:443 - DIRECT/xxx.xxx.xxx.xxx -

So with that said ... Guess all I did was, change the port that Squid was
running on and it works. I would then say that the issue was an ACL on a
upstream router...

Thanks for all of the help.

-----Original Message-----
From: Mark Elsen [mailto:mark.elsen@gmail.com]
Sent: Tuesday, March 28, 2006 12:43 PM
To: Patrick Jones
Cc: squid-users@squid-cache.org
Subject: Re: [squid-users] Squid & SSL on Windows

> Something that I determined is that squid can not handle swithcing
> between http and https as required on the fly. I accessed a site that
> allows initial connections as http and the server erquires that it use
> https, then tells the client that it only allows https, and to please
> reconnect in that manner, but squid does not handle this.

 This requires more thorough verification, to check ; what's going on
exactly by looking at entries in access.log (e.d; the same story).

>
> For my initial issue, I changed the port that Squid was running on and
> ssl is being passed appropriately now. There are still no entries in
> the access log for https...is that because of the "connect" as opposed to
the "get"?

 - There should be, look for :

       ...CONNECT...

  M.
Received on Tue Mar 28 2006 - 10:57:17 MST