You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A server that receives a "close" connection option MUST initiate closure of the connection (see below) after it sends the final response to the request that contained the "close" connection option. The server SHOULD send a "close" connection option in its final response on that connection. The server MUST NOT process any further requests received on that connection.
When Mongoose receives a pipeline with a request containing Connection: close, followed by an invalid request, it closes the connection prematurely, without responding to the first request in the pipeline.
To Reproduce
Start the http-server example.
Send it a pipeline consisting of a valid request with Connection: close set, followed by an invalid request:
Describe the bug
From RFC 9112, section 9.6:
When Mongoose receives a pipeline with a request containing
Connection: close
, followed by an invalid request, it closes the connection prematurely, without responding to the first request in the pipeline.To Reproduce
http-server
example.Connection: close
set, followed by an invalid request:Expected behavior
The server should respond to the first request, and then close the connection.
Logs
Weirdly, the log indicates that the GET request was processed twice. This might be indicative of a deeper problem?
The text was updated successfully, but these errors were encountered: