[squid-users] Re: HTTP/1.1 pipelining

Thanx for clarification. Then to this one, pls:

Trying squid 3.4.3, I get

squidclient -p nnn -U ????? -W ??????? mgr:pconn
HTTP/1.1 200 OK
Mime-Version: 1.0
Date: Fri, 07 Mar 2014 15:15:01 GMT
Content-Type: text/plain
Expires: Fri, 07 Mar 2014 15:15:01 GMT
Last-Modified: Fri, 07 Mar 2014 15:15:01 GMT
Connection: close

 Pool 0 Stats
server-side persistent connection counts:

        req/
        conn count
        ---- ---------
           1 43
           2 5
           4 3
           5 1
           6 2
           7 5
           8 2
           9 2
          10 1
          11 2
          12 1
          13 2
          14 2
          15 1
          17 1
          19 1
          25 1
          26 1
          27 1
          34 1
          36 1
          41 1
          60 1
          70 1
         110 1

 Pool 0 Hash Table
         item 0: 127.0.0.1:8887
         item 1: 127.0.0.1:8887
-------------------------------------------------------------------------------------

Does that mean, absolutely no persistent conn/pipelining to the client (FF,
pipelining enabled; Chrome) ?
from squid.conf:
pipeline_prefetch 3
client_persistent_connections on
http_port nnn tcpkeepalive=3,3,125

BUT:
With almost same squid.conf (besides pipeline_prefetch=on) for my squid2.7
squidclient -p nnn -U ????? -W ??????? mgr:pconn
always shows me quite a few client side persistent conns with request counts
up to about 50.

So either I am missing something in squid.conf, upgraded from 2.7 -> 3.4.3,
a bug in squidclient or a bug/change in behaviour between 2.7/3.4.3 ?
(Note: Using 3.4.3, I can always see "Connection: keep-alive" in the
response header. )

--
View this message in context: http://squid-web-proxy-cache.1019090.n4.nabble.com/HTTP-1-1-pipelining-tp4658574p4665110.html
Sent from the Squid - Users mailing list archive at Nabble.com.