FYI, I finally solved my problem!
It turns out the problem was with PRE-ESTABLISHED connections...
In other words, when I turned on my transparent rules, any Chrome tabs I
had opened BEFORE turning on my transparent proxy rules, apparently would
communicate over a previously opened socket! So the
Ok, I'm using 3.4.9, so I've added that config option to my setup :o)
Thanks for the tip!
Luis
On Sat, Feb 7, 2015 at 6:11 PM, Amos Jeffries wrote:
> On 8/02/2015 5:34 a.m., Luis Miguel Silva wrote:
> > I did when you sent it but it seemed to me you were saying I should add
> > that "reply_head
On 8/02/2015 5:34 a.m., Luis Miguel Silva wrote:
> 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 i
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 do
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
_
Antony,
*Comments inline!*
Thanks,
Luis
On Fri, Feb 6, 2015 at 3:58 PM, Antony Stone <
antony.st...@squid.open.source.it> wrote:
> On Friday 06 February 2015 at 22:54:54 (EU time), Luis Miguel Silva wrote:
>
> > As I started playing around with transparent ssl proxying, I learned that
> > Chrom
On Friday 06 February 2015 at 22:54:54 (EU time), Luis Miguel Silva wrote:
> As I started playing around with transparent ssl proxying, I learned that
> Chrome uses an alternate communication (UDP based) protocol called QUIC.
I'd never heard of QUIC, and http://en.wikipedia.org/wiki/QUIC doesn't
Dear all,
This isn't entirely a squid question but more like a "transparent proxying"
question (which I'm hoping you guys will be able to help me with)...
As I started playing around with transparent ssl proxying, I learned that
Chrome uses an alternate communication (UDP based) protocol called Q
