Project

General

Profile

Actions
Copy link

Bug #6611

closed

RGW: Using underscores when setting headers returns 403

Added by Tyler Brekke over 10 years ago. Updated over 9 years ago.

Status:
Won't Fix
Priority:
Normal
Assignee:
-
Target version:
-
% Done:

0%

Source:
Support
Tags:
Backport:
Regression:
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):

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 ======

Actions
Copy link
 #1

Updated by Yehuda Sadeh over 10 years ago

Did some investigation. The problem originates in apache at ap_create_environment() that normalizes all the env vars that are later being used by the fastcgi module. The fastcgi module is later also trying to do the same (which is useless at that point).

Actions
Copy link
 #2

Updated by Yehuda Sadeh over 9 years ago

  • Status changed from New to Won't Fix

The cgi interface prevents us from doing anything about it. With civetweb it'd be different, but at this point there's not much we can do about.

Actions
Copy link

Also available in: Atom PDF