Interesting, I thought bump server first solved this type of problem. I wonder how is google serving different certs for gmail.com vs mail.google.com at the same IP is this SNI. Is that something squid is likely to support one day? On Sun, Jun 15, 2014 at 6:57 AM, Eliezer Croitoru <eliezer@xxxxxxxxxxxx> wrote: > This is one of the downsides of using ssl-bump. > It's just bumps the IP first before the client and this is one of the side > effects which happens and cannot be prevented for now due to the basic > nature and structure of SSL. > > Eliezer > > > On 06/13/2014 09:56 PM, Douglas Davenport wrote: >> >> I have squid 3.3.10 setup with sslbump working for all sites except >> when a user tries to type in gmail.com. For some reason the browser >> complains about certificate name mismatch. On examination the >> generated cert is actually for mail.google.com. Apparently google is >> redirecting buy why does this error happen only with sslbump. Anyone >> else have this issue, workarounds? >> >> Thanks in advance! >> >
