Project

General

Profile

Actions

Bug #12157

closed

RGW Swift API: responses for several request types don't contain mandatory Content-Type header

Added by Radoslaw Zarzynski almost 9 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Target version:
-
% Done:

0%

Source:
Q/A
Tags:
Backport:
firefly,hammer
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

Description

Swift sends Content-Type HTTP header for all requests even if the response doesn't contain body (in other words: if Content-Length is zero). We have this behaviour implemented until applying some changes in end_header() function. Unfortunately, lack of the header causes early exists of many Tempest's tests for verification of conformance with OpenStack Object Storage API v1.


Related issues 3 (0 open3 closed)

Related to rgw - Bug #12095: RGW Swift API: response for HEAD on container doesn't contain mandatory Content-Type headerDuplicateOrit Wasserman06/19/2015

Actions
Copied to rgw - Backport #12246: RGW Swift API: responses for several request types don't contain mandatory Content-Type headerResolvedOrit Wasserman06/25/2015Actions
Copied to rgw - Backport #13360: RGW Swift API: responses for several request types don't contain mandatory Content-Type headerResolvedRadoslaw ZarzynskiActions
Actions

Also available in: Atom PDF