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: content length #6975

Merged
merged 3 commits into from Jan 5, 2016
Merged

rgw: content length #6975

merged 3 commits into from Jan 5, 2016

Conversation

yehudasa
Copy link
Member

don't send content length on status 204

wido and others added 2 commits December 18, 2015 10:21
RFC7230 says:
  A server MUST NOT send a Content-Length header field in any response with a
  status code of 1xx (Informational) or 204 (No Content).

Fixes: ceph#13582
Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
so that we can avoid atoi() later

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
@ghost
Copy link

ghost commented Dec 18, 2015

@yehudasa please ignore the bot failure, it is a known false negative ( http://tracker.ceph.com/issues/14092 ).

@wido
Copy link
Member

wido commented Dec 19, 2015

Ah, this seems a lot better :) Thanks!

oritwas added a commit that referenced this pull request Jan 5, 2016
@oritwas oritwas merged commit e53f837 into ceph:master Jan 5, 2016
@ghost ghost changed the title Wip rgw content length rgw: content length Feb 10, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants