Description
This is an umbrella ticket for all issues related to connection management and timeouts.
Attachments
Issue Links
- depends upon
-
TS-242 Connect timeout doesn't reset until first byte is received from server
- Open
-
TS-2626 Problem with TS-312 - Always share Keep Alive + NTLM Authorization
- Reopened
-
TS-518 Close UA connection early if the origin sent Connection close:, there's a bad Content-Length header, and the UA connection has Keep-Alive.
- Closed
-
TS-1336 High CPU Usage at idle
- Closed
-
TS-1816 active_timeout may lead TS crash
- Closed
-
TS-1883 TLS origin connections do not support connection timeouts
- Closed
-
TS-2385 http.origin_max_connections is ignored when http.keep_alive_post_out is set
- Closed
-
TS-3299 InactivityCop broken
- Closed
-
TS-3312 KA timeout to origin does not seem to honor configurations
- Closed
-
TS-1334 Congestion control - observed issues
- Patch Available
-
TS-153 "Dynamic" keep-alive timeouts
- Closed
-
TS-54 UnixNet cleanup, encapsulation of event subsystem
- Open
-
TS-754 Reduce memory usage on idle connections
- Open
-
TS-2458 The http transaction should not be rescheduled when the original connections overflow
- Resolved
-
TS-2354 improve documentation about different type of timeouts
- Closed
- is duplicated by
-
TS-3756 Errors on clang analyzer
- Closed
- relates to
-
TS-3487 Cannot override proxy.config.http.transaction_no_activity_timeout_in per remap rule for POST methold
- Closed
- supercedes
-
TS-608 Is HttpSessionManager::purge_keepalives() too aggressive?
- Closed
-
TS-2385 http.origin_max_connections is ignored when http.keep_alive_post_out is set
- Closed
-
TS-3134 proxy.config.net.default_inactivity_timeout is a hack
- Closed
-
TS-1453 remove InactivityCop and enable define INACTIVITY_TIMEOUT
- Closed