[trafficserver] 01/02: Go into timeout state regardless of whether server response data was sent.

[zw...@apache.org]

This is an automated email from the ASF dual-hosted git repository.

zwoop pushed a commit to branch 7.1.x
in repository https://gitbox.apache.org/repos/asf/trafficserver.git

commit 163e3fb91a034fc2729fbd0f0095c2305dc952ef
Author: Susan Hinrichs <sh...@apache.org>
AuthorDate: Mon Mar 19 10:26:01 2018 -0500

    Go into timeout state regardless of whether server response data was sent.
    
    We had issue where client timed out in the POST tunnel state but client_response_hdr_bytes
    was non-zero, so the original post tunnel was not shutdown.  Causing an assert in consumer_handler later.
    
    client_response_hdr_bytes may be set in the setup_100_continue logic, cache logic, and probably a few other
    paths in addition to the receive response header logic.
    
    (cherry picked from commit 60b2d998283e0c05e1270bd1870303f47c52949e)
---
 proxy/http/HttpSM.cc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/proxy/http/HttpSM.cc b/proxy/http/HttpSM.cc
index 7461e39..fb7cf87 100644
--- a/proxy/http/HttpSM.cc
+++ b/proxy/http/HttpSM.cc
@@ -2717,7 +2717,7 @@ HttpSM::tunnel_handler_post(int event, void *data)
 
   switch (event) {
   case HTTP_TUNNEL_EVENT_DONE: // Tunnel done.
-    if (p->handler_state == HTTP_SM_POST_UA_FAIL && client_response_hdr_bytes == 0) {
+    if (p->handler_state == HTTP_SM_POST_UA_FAIL) {
       // post failed
       switch (t_state.client_info.state) {
       case HttpTransact::ACTIVE_TIMEOUT:

-- 
To stop receiving notification emails like this one, please contact
zwoop@apache.org.