[jira] [Updated] (TS-2815) SSL origin server connection hangs if ssl handshake is slow
[ https://issues.apache.org/jira/browse/TS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-2815: --- Fix Version/s: 5.0.0 SSL origin server connection hangs if ssl handshake is slow --- Key: TS-2815 URL: https://issues.apache.org/jira/browse/TS-2815 Project: Traffic Server Issue Type: Bug Components: SSL Reporter: Bryan Call Assignee: Bryan Call Fix For: 5.0.0 When setting the remap to: map / https://www.linkedin.com/ ATS will hang and not write the request to the origin after the ssl handshake has been finished. In the LinkedIn case all the writes happen before the ssl handshake completes. In other test cases, Yahoo, the ssl handshake completes earlier and a write will happen after the handshake and everything is good. The write triggered is set to 0 when the handshake hasn't been completed and will not be re-triggered unless another write happens. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (TS-2815) SSL origin server connection hangs if ssl handshake is slow
[ https://issues.apache.org/jira/browse/TS-2815?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bryan Call updated TS-2815: --- Summary: SSL origin server connection hangs if ssl handshake is slow (was: SSL server connection hangs if ssl handshake is slow) SSL origin server connection hangs if ssl handshake is slow --- Key: TS-2815 URL: https://issues.apache.org/jira/browse/TS-2815 Project: Traffic Server Issue Type: Bug Components: SSL Reporter: Bryan Call When setting the remap to: map / https://www.linkedin.com/ ATS will hang and not write the request to the origin after the ssl handshake has been finished. In the LinkedIn case all the writes happen before the ssl handshake completes. In other test cases, Yahoo, the ssl handshake completes earlier and a write will happen after the handshake and everything is good. The write triggered is set to 0 when the handshake hasn't been completed and will not be re-triggered unless another write happens. -- This message was sent by Atlassian JIRA (v6.2#6252)
