Hello,
I am trying to squeeze a little more performance out of the squid in
http-accelerator mode and wondered about how the persistent connections
worked?
When I first set up the server. I had
server_persistent_connections on
But then I noticed that each apache connection would only serve a sin
On Thu, 1 Sep 2005, Jerry Thomas wrote:
I am trying to squeeze a little more performance out of the squid in
http-accelerator mode and wondered about how the persistent connections
worked?
When I first set up the server. I had
server_persistent_connections on
Good.
But then I noticed that e
Hi:
I am trying to understand Squid behavior when server side connection is
pinned (persistent) and pipelining is enabled on both client and server side
in a transparent proxy configuration.
If there are multiple HTTP requests coming from multiple clients for the
same server and if the requests
I do not believe squid uses a single TCP "Persistent Connection" for more than
1 client at a time, hence the functionality of "Connection Pinning". This is
required to perform things such as NTLM web-based logins.
-
Chad E. Naugle
Tech Support II, x.
ons 2010-09-15 klockan 11:27 -0700 skrev cachenewbie:
> I am trying to understand Squid behavior when server side connection is
> pinned (persistent) and pipelining is enabled on both client and server side
> in a transparent proxy configuration.
In default configuration Squid serializes pipelin
Please keep discussion on the mailinglist.
On Fri, 2 Sep 2005, Jerry Thomas wrote:
Hello Henrik,
You know I tried it again. and the same thing happened. All the apache
processes were waiting for keep alive requests.
I am using custom compiled version/removed open ssl since I did not need
it.
