[squid-users] https issues for google

[Eliezer Croitoru]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hey Glenn,

I noticed that in the mean while you have upgraded the system to
latest 3.4.9 stable.
As Amos mentioned there are couple options about the tunneling issues.
I am unsure about the issue since in my environment squid seems to not
have any issues.
I would suggest a testing path for the issue before applying patches
blindly.
My suggestion is:
- - use one and only one client
- - run a tracepath from the client to the relevant sites.
- - test using wget\curl\script a tunnel request to
https:/www.gmail.com/ or https://mail.google.com/ throw the proxy from
the mentioned client.(there is a wget binary for windows)
- - if the issue accrues to this client try to remove the authentication
only for this client ip and try again.

The above test will isolate the issue from multiple clients and
unknown source to only one.
If you are familiar with PMTU or iptables clamping it will help to
test it more in depth.
I assume that you are using a Linux OS and I would prefer to get some
details about it as a starter.

Thanks,
Eliezer

On 10/09/2014 02:04 AM, glenn.groves at bradnams.com.au wrote:
> Could squid be getting mixed up when mulipule https requests are to
> the same address (e.g. https://google.com.au)?
> 
> Thanks,
> 
> Glenn

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQEcBAEBAgAGBQJUhNWkAAoJENxnfXtQ8ZQUhjkIAIt13ZuSaMx7HyLYExUmAxPW
djzEj9DK6YBEUexeSA5hfIqRFwA0wRXK1a4fAni8J5v7iVqqdLj4Cwnx1C3Jf9Gc
fl9pRBbDNl8SMHWUPvxv0PELRgGzjGN76CXHB7aARbAKaOd6raajlbdl0ltro2D6
UyTaAjG2lc2yH/kJAGHsnjpEztkxWezdBWO3SC8Ej4bEdctfRfSEXeZDI0fQsSsg
D3vVG/ppGOSnivMfeQiaUSmexhaFI6XO0wrrj4uyeJ/ptVC0ZkikkCDCp3xRWEAt
BK0fgRJtUbc7jroqPx7ec+2l3gtZCbK8fMDwPMt2ut5IXevPFO8B4a16dPk40uM=
=6hKW
-----END PGP SIGNATURE-----