d3ce225 created the issue
When updating an object to set custom headers and setting the "Access-Control-Allow-Origin" header, on download that header is clobbered to "x-object-meta-access-control-allow-origin". When setting this header using the Rackspace API, it does not get altered in any way.
To reproduce, open CD, connect to Swift, open a container and select an object, right-click Info, Metadata, add Custom Header:
name: "Access-Control-Allow-Origin"
value: http://domain.foo
Then download the object:
curl -v http://cXXXX.rXX.cfX.rackcdn.com/filename
* About to connect() to c3240.6e34c3667c4e6e5a72b9bda89e6718932100ab31.cf2.rackcdn.com port 80 (#0)
* Trying 96.17.106.113... connected
<snip>
< HTTP/1.1 200 OK
< Server: nginx/0.7.65
< Content-Type: image/jpeg
< Content-Length: 19251
< x-object-meta-access-control-allow-origin: http%3A%2F%2Fdomain.foo
Attachments
When updating an object to set custom headers and setting the "Access-Control-Allow-Origin" header, on download that header is clobbered to "x-object-meta-access-control-allow-origin". When setting this header using the Rackspace API, it does not get altered in any way.
To reproduce, open CD, connect to Swift, open a container and select an object, right-click Info, Metadata, add Custom Header:
Then download the object:
Attachments
Allow_setting_non_meta_headers.patch(16.1 KiB)