Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

rgw: Properly respond to the Connection header with Civetweb #5284

Merged
1 commit merged into from Jul 31, 2015

Conversation

smithfarm
Copy link
Contributor

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: ceph#12298
(cherry picked from commit 79197d3)
@smithfarm smithfarm self-assigned this Jul 19, 2015
@smithfarm smithfarm added this to the hammer milestone Jul 19, 2015
@smithfarm smithfarm assigned theanalyst and unassigned smithfarm Jul 19, 2015
ghost pushed a commit that referenced this pull request Jul 19, 2015
…der with Civetweb

Reviewed-by: Loic Dachary <ldachary@redhat.com>
@ghost
Copy link

ghost commented Jul 28, 2015

@yehudasa does this hammer backport looks good to merge ? It went through a rgw suite ( http://tracker.ceph.com/issues/11990#rgw ), only one job failed because of a radosgw-agent failure specific to Ubuntu 12.04 (but succeded on 14.04).

ghost pushed a commit that referenced this pull request Jul 29, 2015
ghost pushed a commit that referenced this pull request Jul 31, 2015
rgw: Properly respond to the Connection header with Civetweb

Reviewed-by: Yehuda Sadeh <ysadehwe@redhat.com>
@ghost ghost merged commit 99ca62f into ceph:hammer Jul 31, 2015
@smithfarm smithfarm deleted the wip-12398-hammer branch July 31, 2015 19:01
This pull request was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants