Bug #12298
rgw: Properly respond to the "Connection" header with Civetweb
0%
Description
HTTP 1.1 assumes KeepAlive if the 'Connection' header is not set.
If the client however sends 'Connection: close' the server should respond with the same header and close the connection.
This will cause the client to also close the connection.
The RGW currently only responds with the 'keep-alive' value if that was send by the client, but it doesn't do anything else.
Related issues
Associated revisions
rgw: If the client sends a Connection: close header respond accordingly.
HTTP/1.1 assumes Keep-Alive by default, but if a Connection: close header is send
the server should respond with it as well.
This makes the client close the connection after the request.
Fixes: #12298
rgw: If the client sends a Connection: close header respond accordingly.
HTTP/1.1 assumes Keep-Alive by default, but if a Connection: close header is send
the server should respond with it as well.
This makes the client close the connection after the request.
Fixes: #12298
(cherry picked from commit 79197d3711edc4b04a7ea4335b6e1b65754996d5)
History
#1 Updated by Yehuda Sadeh over 8 years ago
- Backport set to hammer
#2 Updated by Yehuda Sadeh over 8 years ago
- Status changed from New to Pending Backport
#3 Updated by Nathan Cutler over 8 years ago
#4 Updated by Nathan Cutler over 8 years ago
- Status changed from Pending Backport to Resolved