Bug 170399 - Squid blocks page served by broken server
Squid blocks page served by broken server
Product: Red Hat Enterprise Linux 4
Classification: Red Hat
Component: squid (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Martin Stransky
Depends On: 163595
Blocks: 168429
  Show dependency treegraph
Reported: 2005-10-11 06:58 EDT by Martin Stransky
Modified: 2007-11-30 17:07 EST (History)
2 users (show)

See Also:
Fixed In Version: RHSA-2006-0052
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-03-07 13:50:19 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 Martin Stransky 2005-10-11 06:58:38 EDT
+++ This bug was initially created as a clone of Bug #163595 +++

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.9) Gecko/20050711

Description of problem:
Recent Squid updates introduced a new stricter handling of HTTP level protocoll
errors which results in many broken sites being closed out. While in fact those
sites are broken, the squid developers realized that the changes made were too
strict and released the relaxed_header_parser patch in squid-2.5.STABLE8 to make
things work again in most situations.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1. check a broken site like

Actual Results:  squid reports this in /var/log/squid/cache.log:
2005/07/19 12:43:38| ctx: enter level  0:
2005/07/19 12:43:38| WARNING: unparseable HTTP header field near {HTTP/1.0 200 OK
Content-type: text/html
2005/07/19 12:48:18| ctx: exit level  0

Of course, the page does not load in the client browser.

Expected Results:  An error should go to /var/log/squid/cache.log but in this
case the page should load fine in the client browser anyway.

Additional info:

I have built my own squid rpm with a backported patch of
for new. I strongly suggest that this patch is included into the next update.
I'll attach the files.

-- Additional comment from simon.matter@ch.sauter-bc.com on 2005-07-19 07:28 EST --
Created an attachment (id=116923)
Update spec file which includes backported relaxed_header_parser patch

-- Additional comment from simon.matter@ch.sauter-bc.com on 2005-07-19 07:30 EST --
Created an attachment (id=116924)
squid-2.5.STABLE8-relaxed_header_parser.patch backported to STABLE3

-- Additional comment from ptsjohol@cc.jyu.fi on 2005-08-30 05:12 EST --
This bug also exists in RHEL 4, so please fix it. =)

-- Additional comment from simon.matter@ch.sauter-bc.com on 2005-08-30 05:19 EST --
You are right, I have also built my own patched RHEL 4 squid package. However, I
really expect this fix in the next official squid rpms.

-- Additional comment from stransky@redhat.com on 2005-08-30 05:23 EST --
It's planned for the next update.
Comment 4 Red Hat Bugzilla 2006-03-07 13:50:20 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.