> 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.
