Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1093072

Summary: Issues with timeout on HTTPS connections.
Product: Red Hat Enterprise Linux 6 Reporter: Chris Pelland <cpelland>
Component: squidAssignee: Pavel Šimerda (pavlix) <psimerda>
Status: CLOSED DEFERRED QA Contact: Ondřej Pták <optak>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: cpelland, jhouska, jkurik, jsvarova, mkrcmari, optak, ovasik, pm-eus, psimerda, sgordon
Target Milestone: rcKeywords: ZStream
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Squid can be configured to use the SPICE protocol for establishing long-term data connections. Previously, Squid terminated its connections through the SPICE protocol prematurely every 15 minutes. As a consequence, any data transfer that lasted more than 15 minutes could be interrupted. The underlying source code has been fixed, and Squid no longer terminates long-term data connections when proxied through the SPICE protocol.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-09 08:48:13 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:
Bug Depends On: 1039088    
Bug Blocks: 871829    

Description Chris Pelland 2014-04-30 14:28:08 UTC
This bug has been copied from bug #1039088 and has been proposed
to be backported to 6.5 z-stream (EUS).

Comment 5 Ondřej Pták 2014-05-13 14:12:36 UTC
Marian Krcmarik from spice qe wrote in original Bug 1039088:
"""
I am not able to verify the bug with the original reproducer this bug was reported with.
If I open Spice SSL session through squid proxy which tunnels spice traffic to the hosts with configuration item "read_timeout 30 seconds" then connection is terminated after the 30 seconds -  on both current shipped and the new brew squid builds.
"""

I found neither regression with this patch, nor any difference from previous version.

Comment 9 Jan Kurik 2014-06-09 08:48:13 UTC
Closing this bug as the ystream bug went back to non-fixed state. Once the ystream bug is fixed, I am open to create a new clone, if needed.