Project

General

Profile

Actions
Copy link

Bug #12298

closed

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

Added by Wido den Hollander almost 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Wido den Hollander
Target version:
-
% Done:

0%

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

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 1 (0 open — 1 closed)

Copied to rgw - Backport #12398: rgw: Properly respond to the "Connection" header with CivetwebResolvedWido den Hollander07/13/2015Actions
Actions
Copy link
 #1

Updated by Yehuda Sadeh almost 9 years ago

  • Backport set to hammer
Actions
Copy link
 #2

Updated by Yehuda Sadeh almost 9 years ago

  • Status changed from New to Pending Backport
Actions
Copy link
 #4

Updated by Nathan Cutler over 8 years ago

  • Status changed from Pending Backport to Resolved
Actions
Copy link

Also available in: Atom PDF