From eddd48b783c670f48d39c4858e5d800bea95a1f7 Mon Sep 17 00:00:00 2001 From: Tatsuhiro Tsujikawa Date: Fri, 1 Mar 2013 20:43:35 +0900 Subject: [PATCH] shrpx: Don't issue RST_STREAM on downstream tunnel connection EOF The RST_STREAM will be issued in spdy_data_read_callback. --- src/shrpx_spdy_upstream.cc | 7 +------ 1 file changed, 1 insertion(+), 6 deletions(-) diff --git a/src/shrpx_spdy_upstream.cc b/src/shrpx_spdy_upstream.cc index 08afc8c..78d7946 100644 --- a/src/shrpx_spdy_upstream.cc +++ b/src/shrpx_spdy_upstream.cc @@ -563,12 +563,7 @@ void spdy_downstream_eventcb(bufferevent *bev, short events, void *ptr) // response body is sent. This is needed to ensure that // RST_STREAM is sent after all pending data are sent. upstream->on_downstream_body_complete(downstream); - } else if(downstream->get_response_state() == Downstream::MSG_COMPLETE) { - if(downstream->tunnel_established()) { - // For SSL tunneling - upstream->rst_stream(downstream, SPDYLAY_INTERNAL_ERROR); - } - } else { + } else if(downstream->get_response_state() != Downstream::MSG_COMPLETE) { // If stream was not closed, then we set MSG_COMPLETE and let // on_stream_close_callback delete downstream. if(upstream->error_reply(downstream, 502) != 0) {