[
https://issues.apache.org/jira/browse/TS-2211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13775713#comment-13775713
]
Alan M. Carroll commented on TS-2211:
-------------------------------------
I must admit, I am a bit unclear on what this code is doing exactly, but here's
the first patch (and sorry for the patch misapplication).
{code}
- if (s->vio.ntodo() <= 0 || !buf.reader()->read_avail()) {
- write_disable(nh, vc);
- return;
- }
+ }
+ if (!buf.reader()->read_avail()) {
+ write_disable(nh, vc);
+ return;
{code}
The {{if (s->vio.ntodo() <= 0)}} check is removed entirely (the other clause is
checked later, in the added code). While ntodo() has been checked and found {{>
0}} just previously, {{write_signal_and_update}} has been called since then and
that might have changed ntodo() if it returned {{EVENT_CONT}}.
> SSL client connections hang and a aborted due to inactivity
> -----------------------------------------------------------
>
> Key: TS-2211
> URL: https://issues.apache.org/jira/browse/TS-2211
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, SSL
> Reporter: Theo Schlossnagle
> Fix For: 4.1.0
>
> Attachments:
> 0001-TS-2211-SSL-client-connections-hang-and-a-aborted-du.patch,
> 0002-TS-2211-SSL-client-connections-hang-and-a-aborted-du.patch
>
>
> Test setup:
> ATS in reverse proxy mode. Terminating SSL for clients, remap to non-SSL for
> origin. Origin delays 10s before sending any data (including headers), then
> dumps a non-chunked response (Content-Length) of about 3Mbytes.
> Over slow client connections, the client session freezes mid download (around
> 256k in my tests)... hangs until the inactivity timer fires and snips all the
> connections.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
