Bug 74068

Summary: Privoxy won't allow display of CUPS website correctly
Product: [Retired] Red Hat Linux Reporter: Joshua Jensen <joshua>
Component: privoxyAssignee: Karsten Hopp <karsten>
Status: CLOSED RAWHIDE QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 9CC: twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2003-07-09 12:46:35 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Joshua Jensen 2002-09-14 14:51:40 UTC 
Description of Problem:

When mozilla uses provoxy, and you surf to http://localhost:631, the page never
fully loads.  Disabling privoxy allows things to work well.

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

stock Psyche pre-respin
Comment 1 Joshua Jensen 2003-01-03 17:23:21 UTC 
This seems to be true for the public beta too
Comment 2 Karsten Hopp 2003-07-09 12:46:35 UTC 
one of the privoxy maintainers had a look at this and wrote that 
"Cups' httpd ignores Privoxy's "Connection: close" header and tries 
Keep-Alive, which if true would point at a bug in cups." 
 
His current workaround is to add the following lines to the privoxy rules: 
 
{+downgrade-http-version} 
:631