Bug #6611
closedRGW: Using underscores when setting headers returns 403
0%
Description
When setting headers that contain an underscore rgw returns a 403
In this example the header set was {'x-amz-meta-test_header':'testing'}
2013-10-22 13:56:17.606256 7fb4e0fc9700 10 auth_hdr:
PUT
application/octet-stream
Tue, 22 Oct 2013 20:56:19 GMT
x-amz-copy-source:my_bucket%2Fnew%20file
x-amz-meta-test-header:testing
x-amz-metadata-directive:REPLACE
/my_bucket/new%20file
2013-10-22 13:56:17.606367 7fb4e0fc9700 15 calculated digest=2wLp1lWRkER8daKwu8FV1ec5XeA=
2013-10-22 13:56:17.606372 7fb4e0fc9700 15 auth_sign=Vea98DmlXZmOWlF0d5UI5HQ8kDE=
2013-10-22 13:56:17.606375 7fb4e0fc9700 15 compare=36
2013-10-22 13:56:17.606380 7fb4e0fc9700 10 failed to authorize request
2013-10-22 13:56:17.606427 7fb4e0fc9700 2 req 181:0.000753:s3:PUT /my_bucket/new%20file:copy_obj:http status=403
2013-10-22 13:56:17.606569 7fb4e0fc9700 1 ====== req done req=0x1fd0020 http_status=403 ======