Bug 170399

+++ 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
Firefox/1.0.5

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):
squid-2.5.STABLE3-6.3E.13

How reproducible:
Always

Steps to Reproduce:
1. check a broken site like
http://www.topjobs.ch/app/site.exe?FmAction=CompanyJobs&ClnId=1580
2.
3.
  

Actual Results:  squid reports this in /var/log/squid/cache.log:
2005/07/19 12:43:38| ctx: enter level  0:
'http://www.topjobs.ch/app/site.exe?FmAction=CompanyJobs&ClnId=1580'
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
http://www.squid-cache.org/Versions/v2/2.5/bugs/squid-2.5.STABLE8-relaxed_header_parser.patch
for new. I strongly suggest that this patch is included into the next update.
I'll attach the files.

-- Additional comment from simon.matter.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.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.fi on 2005-08-30 05:12 EST --
This bug also exists in RHEL 4, so please fix it. =)

-- Additional comment from simon.matter.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 on 2005-08-30 05:23 EST --
It's planned for the next update.