Date: Wed, 27 Dec 2006 16:05:49 -0800 From: Colin Percival <cperciva@freebsd.org> To: Chuck Swiger <cswiger@mac.com> Cc: Max Laier <max@love2party.net>, Adam McDougall <mcdouga9@egr.msu.edu>, freebsd-current@freebsd.org, Mike Silbersack <silby@silby.com> Subject: Re: Fwd: Re: pf: BAD state happens often with portsnap fetch update Message-ID: <45930A5D.1080602@freebsd.org> In-Reply-To: <4592FF0A.1080400@mac.com> References: <20061210010823.GS81923@egr.msu.edu> <20061214172323.GP1011@egr.msu.edu> <45908ED3.4040503@freebsd.org> <200612261129.48173.max@love2party.net> <459192A9.2050808@freebsd.org> <4592FF0A.1080400@mac.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Chuck Swiger wrote: > FYI, if you pass a: > > Connection: keep-alive > > ...header in the request, Squid will not close the client->proxy > connection and you ought to be able to re-use it to make additional > requests. In HTTP/1.1, connections are assumed to be persistent unless declared otherwise. > PS: Squid "supports HTTP/1.0 persistent connections", from which the HTTP/1.1 > style keepalives derive-- and quick testing suggests these persistent > connections work with either HTTP/1.0 or 1.1 specified in the request. Grr. I hate adding workarounds to improve compatibility with hopelessly antique code (seriously, why doesn't squid support http/1.1 yet?), but I guess I'll make phttpget emit a completely bogus "Connection: Keep-Alive" header to go along with its HTTP/1.1 requests. Colin Percival
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?45930A5D.1080602>