[squid-users] Blocking Chrome and QUIC

[Luis Miguel Silva]

I did when you sent it but it seemed to me you were saying I should add
that "reply_header_access Alternate-Protocol deny all" config parameter
but, on the other hand, I didn't understand why were you suggesting that,
seeing that my problem is that Chrome doesn't go through my proxy at all!
(I'm doing transparent proxying, NOT setting up a proxy in Chrome).

I've now re-read your email and it seemed you were telling me to upgrade to
3.5.x (which I hadn't understood the last time I read your email). I
apologize that I didn't understand what you were saying.

So are you saying I must upgrade to Squid 3.5.x to fix this? Why would that
header fix it, seeing that my problem is that Chrome is bypassing the proxy
altogether?

Thank you,
Luis

On Sat, Feb 7, 2015 at 1:17 AM, Amos Jeffries <squid3 at treenet.co.nz> wrote:

> On 7/02/2015 5:41 p.m., Luis Miguel Silva wrote:
> > Antony,
> >
> > *Comments inline!*
> >
>
> Did you see the reply I sent a few days ago?
>
> ... in your previous thread entitled "SSL-bump certificate issues
> (mostly on Chrome, when accessing Google websites) "
>
> Amos
> _______________________________________________
> squid-users mailing list
> squid-users at lists.squid-cache.org
> http://lists.squid-cache.org/listinfo/squid-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20150207/3efec877/attachment.html>