Description of problem: Swift expects a Content-Length header on a container creation request How reproducible: always Steps to Reproduce: 1. Create a container (bucket) through the swift api Actual results: No Content-Length header in the response (chunked response). Expected results: Content-Length header in the response Additional info: Fixed upstream
Fcgi is not 1.3, it is 1.2.z, adjusting accordingly. Yehuda, please flag if I am wrong.
need qa_ack
tested this on 1.2.4 on magna016, still seeing the same error, [ubuntu@magna016 ~]$curl -X PUT -H "X-Auth-Token: AUTH_rgwtk0e00000074657374757365723a73776966747d04ffb8446e91dddb79cd5578527d12247f78316f225f238b834e9eebf3b8ad8a60b43a" -H "X-Container-Read: .r:*" http://10.8.128.16/swift/v1/nwq/nano MissingContentLength
The response your seeing is what we return because you didn't provide content length in the request, not really related to the actual big you're testing. You need to provide content length header to the request, and then see whether we return the appropriate header.
yes, verified this bug and looks good, [ubuntu@magna016 ~]$ curl -i http://10.8.128.16/swift/v1/my-new-buckets -X PUT -H "Content-Length: 0" -H "X-Auth-Token: AUTH_rgwtk0e00000074657374757365723a73776966747d04ffb8446e91dddb79cd5578527d12247f78316f225f238b834e9eebf3b8ad8a60b43a" HTTP/1.1 201 Created Date: Thu, 13 Aug 2015 22:47:54 GMT Accept-Ranges: bytes Content-Length: 0 Connection: close Content-Type: text/plain; charset=utf-8
Works on 1.2.3.2 trusty and precise
Failed on Centos 6.7 On Centos 6.7 I ran the commands below and got a zero length value 1. create a bucket 2. curl -i http://<ip of the rgw host>/swift/v1/<bucket_name> -X PUT -H "Content-Length: 0" -H "X-Auth-Token: <Auth-token>" [inorder to find auth token, use the swift command below, swift -A http://{IP ADDRESS}/auth/1.0 -U testuser:swift -K '{swift_secret_key}' stats -v ] 3. verify the content-length is displayed in the output.
Whoops. looks like zero length is correct. Passed on Centos 6.7
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2015-1703.html