On 01/15/2018 02:12 PM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 13:48 -0700, Alex Rousskov wrote:
>>
>> both transparent and forward/explicit proxies have approximately the same
>> support for HTTPS. In other words, if you find a forward/explicit
>> proxy useful for HTTPS, then a
On Mon, 2018-01-15 at 13:48 -0700, Alex Rousskov wrote:
>
> That statement does not compute in the current context: A transparent
> proxy has many disadvantages over a forward/explicit proxy,
Sure. But it has advantages also.
> but both
> transparent and forward/explicit proxies have
On 01/15/2018 12:31 PM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 12:26 -0700, Alex Rousskov wrote:
>> What about the transparent proxy part?
> I already have that, but that is becoming more or less useless in the
> everything-https world we are heading towards since you can't
>
On Mon, 2018-01-15 at 12:26 -0700, Alex Rousskov wrote:
>
> What about the transparent proxy part?
I already have that, but that is becoming more or less useless in the
everything-https world we are heading towards since you can't
transparently proxy https. AFAIU.
> if Squid closed a CONNECT
On 01/15/2018 11:32 AM, Brian J. Murrell wrote:
> On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
>> On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
>>> On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
In that case, there are two HTTP connections in play:
1. An HTTP
On 16/01/18 07:32, Brian J. Murrell wrote:
On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
In that case, there are two HTTP connections in play:
1. An HTTP connection from the
On Mon, 2018-01-15 at 10:56 -0700, Alex Rousskov wrote:
> On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
> > On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
> > > In that case, there are two HTTP connections in play:
> > >
> > > 1. An HTTP connection from the client to the origin
> >
On 01/15/2018 08:40 AM, Brian J. Murrell wrote:
> On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
>> In that case, there are two HTTP connections in play:
>>
>> 1. An HTTP connection from the client to the origin server.
> By this do you mean to say there is a connection from the
On Mon, 2018-01-15 at 16:06 +, Rafael Akchurin wrote:
> Hello Brian,
Hi,
> *but* the same 200 of tabs loads just fine from FF and the same Squid
> on the same machine at the same time - so might be a Chrome
> issue/architecture?
Interesting. I'm not sure how I would do it, but it would be
quid-users] persistent connections not being utilized with Chrome
On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
> In that case, there are two HTTP
> connections
> in play:
>
> 1. An HTTP connection from the client to the origin server.
By this do you mean to say t
On Fri, 2018-01-12 at 21:34 -0700, Alex Rousskov wrote:
> In that case, there are two HTTP
> connections
> in play:
>
> 1. An HTTP connection from the client to the origin server.
By this do you mean to say there is a connection from the client,
through the proxy server to the origin server?
On 01/12/2018 08:23 PM, Brian J. Murrell wrote:
> I mean, will not actually result in a persistent connection -- a socket
> that is reused for multiple HTTP transactions.
It is best to think of HTTP persistency as applying to an HTTP
connection rather than a TCP connection/socket. Without a
On Sat, 2018-01-13 at 13:15 +1300, Amos Jeffries wrote:
>
> What do you mean "not available for?
I mean, will not actually result in a persistent connection -- a socket
that is reused for multiple HTTP transactions. I suppose for CONNECT
it would mean either multiple CONNECTs within a single
On 13/01/18 03:52, Brian J. Murrell wrote:
I am noticing that my Squid 3.5.20 installation is not utilizing
persistent connections with a Chrome browser user. My Squid
configuration is not disabling the default status of persistent
connections being enabled.
I can see Chrome including
I am noticing that my Squid 3.5.20 installation is not utilizing
persistent connections with a Chrome browser user. My Squid
configuration is not disabling the default status of persistent
connections being enabled.
I can see Chrome including "Proxy-Connection: keep-alive" in it's
request and
15 matches
Mail list logo
