shrpx: Don't issue RST_STREAM on downstream tunnel connection EOF
The RST_STREAM will be issued in spdy_data_read_callback.
This commit is contained in:
parent
2d23ae3741
commit
eddd48b783
|
@ -563,12 +563,7 @@ void spdy_downstream_eventcb(bufferevent *bev, short events, void *ptr)
|
||||||
// response body is sent. This is needed to ensure that
|
// response body is sent. This is needed to ensure that
|
||||||
// RST_STREAM is sent after all pending data are sent.
|
// RST_STREAM is sent after all pending data are sent.
|
||||||
upstream->on_downstream_body_complete(downstream);
|
upstream->on_downstream_body_complete(downstream);
|
||||||
} else if(downstream->get_response_state() == Downstream::MSG_COMPLETE) {
|
} else if(downstream->get_response_state() != Downstream::MSG_COMPLETE) {
|
||||||
if(downstream->tunnel_established()) {
|
|
||||||
// For SSL tunneling
|
|
||||||
upstream->rst_stream(downstream, SPDYLAY_INTERNAL_ERROR);
|
|
||||||
}
|
|
||||||
} else {
|
|
||||||
// If stream was not closed, then we set MSG_COMPLETE and let
|
// If stream was not closed, then we set MSG_COMPLETE and let
|
||||||
// on_stream_close_callback delete downstream.
|
// on_stream_close_callback delete downstream.
|
||||||
if(upstream->error_reply(downstream, 502) != 0) {
|
if(upstream->error_reply(downstream, 502) != 0) {
|
||||||
|
|
Loading…
Reference in New Issue