Bug 168377

Summary: squid "pipeline_prefetch on" instability
Product: [Fedora] Fedora Reporter: Josh Bressers <bressers>
Component: squidAssignee: Martin Stransky <stransky>
Status: CLOSED ERRATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: 4Keywords: Security
Target Milestone: ---   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard: impact=moderate,reported=20050915,public=20050915,source=squid
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2005-09-23 16:23:08 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 Josh Bressers 2005-09-15 14:59:35 UTC 
+++ This bug was initially created as a clone of Bug #168376 +++

This issue comes from upstream:

http://www.squid-cache.org/Versions/v2/2.5/bugs/#squid-2.5.STABLE10-pipeline-CONNECT

It seems that it is possible for the server to enter an unknown state when
"pipeline_prefetch on" is set in the configuration file.  We do not turn this on
by default.  I'm not completely sure what the result of this issue is.
Comment 1 Josh Bressers 2005-09-15 15:00:24 UTC 
This issue should also affect FC3