Project

General

Profile

Bug #12298

rgw: Properly respond to the "Connection" header with Civetweb

Added by Wido den Hollander about 4 years ago. Updated about 4 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
Start date:
07/13/2015
Due date:
% Done:

0%

Source:
other
Tags:
keepalive,civetweb
Backport:
hammer
Regression:
No
Severity:
2 - major
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:

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

Copied to rgw - Backport #12398: rgw: Properly respond to the "Connection" header with Civetweb Resolved 07/13/2015

Associated revisions

Revision 79197d37 (diff)
Added by Wido den Hollander about 4 years ago

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

Revision 2357b6c8 (diff)
Added by Wido den Hollander about 4 years ago

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 about 4 years ago

  • Backport set to hammer

#2 Updated by Yehuda Sadeh about 4 years ago

  • Status changed from New to Pending Backport

#4 Updated by Nathan Cutler about 4 years ago

  • Status changed from Pending Backport to Resolved

Also available in: Atom PDF