[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 6.2.0) 7.0.0 > Connect timeout doesn't reset until first byte is received from server > -- > > Key: TS-242 > URL: https://issues.apache.org/jira/browse/TS-242 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Steve Jiang >Assignee: Leif Hedstrom >Priority: Minor > Fix For: 7.0.0 > > > proxy.config.http.connect_attempts_timeout > proxy.config.http.parent_proxy.connect_attempts_timeout > proxy.config.http.post_connect_attempts_timeout > These timeouts are implemented with inactivity timeout on the netvc and don't > behave as expected. > If the connect succeeds (the remote server successfully accepted) but the > remote server does not respond with any bytes within the timeout period, TS > still treats it as a connect timeout. If retries are enabled and the origin > server is slow to start sending responses (but not down), it will keep > sending requests and closing the connection after getting no response within > the connect timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 6.1.0) 6.2.0 > Connect timeout doesn't reset until first byte is received from server > -- > > Key: TS-242 > URL: https://issues.apache.org/jira/browse/TS-242 > Project: Traffic Server > Issue Type: Bug > Components: Core >Reporter: Steve Jiang >Assignee: Leif Hedstrom >Priority: Minor > Fix For: 6.2.0 > > > proxy.config.http.connect_attempts_timeout > proxy.config.http.parent_proxy.connect_attempts_timeout > proxy.config.http.post_connect_attempts_timeout > These timeouts are implemented with inactivity timeout on the netvc and don't > behave as expected. > If the connect succeeds (the remote server successfully accepted) but the > remote server does not respond with any bytes within the timeout period, TS > still treats it as a connect timeout. If retries are enabled and the origin > server is slow to start sending responses (but not down), it will keep > sending requests and closing the connection after getting no response within > the connect timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 6.0.0) 6.1.0 Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Assignee: Alan M. Carroll Priority: Minor Fix For: 6.1.0 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Assignee: (was: Alan M. Carroll) Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Priority: Minor Fix For: 6.1.0 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Susan Hinrichs updated TS-242: -- Fix Version/s: (was: 5.3.0) sometime Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Assignee: Alan M. Carroll Priority: Minor Fix For: sometime proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 6.0.0) 5.3.0 Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Assignee: Alan M. Carroll Priority: Minor Fix For: 5.3.0 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 3.1.3) 3.3.0 Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Assignee: Alan M. Carroll Priority: Minor Fix For: 3.3.0 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: (was: 3.1.1) 3.1.2 Moving these to 3.1.2 for now. please move back if they will be worked on asap for 3.1.1. Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Assignee: Alan M. Carroll Priority: Minor Fix For: 3.1.2 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (TS-242) Connect timeout doesn't reset until first byte is received from server
[ https://issues.apache.org/jira/browse/TS-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Leif Hedstrom updated TS-242: - Fix Version/s: 2.1.2 Connect timeout doesn't reset until first byte is received from server -- Key: TS-242 URL: https://issues.apache.org/jira/browse/TS-242 Project: Traffic Server Issue Type: Bug Components: Core Reporter: Steve Jiang Priority: Minor Fix For: 2.1.2 proxy.config.http.connect_attempts_timeout proxy.config.http.parent_proxy.connect_attempts_timeout proxy.config.http.post_connect_attempts_timeout These timeouts are implemented with inactivity timeout on the netvc and don't behave as expected. If the connect succeeds (the remote server successfully accepted) but the remote server does not respond with any bytes within the timeout period, TS still treats it as a connect timeout. If retries are enabled and the origin server is slow to start sending responses (but not down), it will keep sending requests and closing the connection after getting no response within the connect timeout. -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.
