Bug 150781 - Squid doesn't handle headers split across packets
Squid doesn't handle headers split across packets
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: squid (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Depends On:
Blocks: 168424
  Show dependency treegraph
Reported: 2005-03-10 10:35 EST by Robert Clark
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2006-0045
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-15 10:41:54 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Robert Clark 2005-03-10 10:35:52 EST
This is with squid-2.5.STABLE3-6.3E.8

Squid doesn't cope with HTTP response headers which are split across different
TCP packets.

Observed proxying to http://www.iii.co.uk/
Produces the following error (intermittantly):

2005/03/10 10:59:01| WARNING: unparseable HTTP header field near {: Thu, 10 Mar
2005 10:58:59 GMT
Server: Apache/1.3.22 (Unix) AxKit/1.4_82 mod_perl/1.26 mod_gzip/
Vary: X-HOST
Expires: now
Pragma: no-cache
: no-cache,no-store,private
Content-Type: text/html
Content-Encoding: gzip
: 18064

The missing parts of the headers are being sent by the origin server but are
lost by squid.

This is a known issue and the patch to fix it is available at:

I've tested this and it applies cleanly to the current SRPM and fixes the problem.
Comment 4 Martin Stransky 2005-11-15 07:27:47 EST
The new release-candidate packages for RHEL3/4 are available here:

Comment 7 Red Hat Bugzilla 2006-03-15 10:41:55 EST
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on the solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.


Note You need to log in before you can comment on or make changes to this bug.