Bug 1093072
| Summary: | Issues with timeout on HTTPS connections. | ||
|---|---|---|---|
| Product: | Red Hat Enterprise Linux 6 | Reporter: | Chris Pelland <cpelland> |
| Component: | squid | Assignee: | Pavel Šimerda (pavlix) <psimerda> |
| Status: | CLOSED DEFERRED | QA Contact: | Ondřej Pták <optak> |
| Severity: | high | Docs Contact: | |
| Priority: | high | ||
| Version: | 6.5 | CC: | cpelland, jhouska, jkurik, jsvarova, mkrcmari, optak, ovasik, pm-eus, psimerda, sgordon |
| Target Milestone: | rc | Keywords: | 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
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. 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. |