On Sat, 2005-09-10 at 23:54 +0200, Henrik Nordstrom wrote:
The corresponding(?) bugzilla comment says
... uncovered another HTTP compliance bug in Squid where HTTP/1.1
messages was considered (partly) as implicitly keep-alive even if Squid is
still HTTP/1.0.
What is wrong with
On Wed, 7 Sep 2005, Alex Rousskov wrote:
Should it be named WHEN_SQUID_IS_HTTP1_1 instead?
Probably. It is in the 2.5 version..
Can the intended semantics of httpMsgIsPersistent() be summarized as
The HTTP agent sending the supplied message
wants to keep the connection
HTTP/1.0 keep-alive can not be enabled unless the request explicitly says
this is understood by the requestor. HTTP/1.1 alone does not imply that the
requestor implements HTTP/1.1 keep-alive as the signaling methods of HTTP/1.1
I obviously meant to say requestor implements HTTP/1.0
Hello,
I have a couple of questions about WHEN_SQUID_IS_NOT_HTTP1_1
#define that was added to HttpMsg.cc while fixing now-closed bug #890:
http://www.squid-cache.org/bugs/show_bug.cgi?id=890
http://www.squid-cache.org/cgi-bin/cvsweb.cgi/squid3/src/HttpMsg.cc.diff?r1=1.13r2=1.14f=h
Should
