registry team mailing list archive

[clayg <clay.gerrard@xxxxxxxxxxxxx>]

Public bug reported:

The cf-devguide specifically says:
"You cannot use the POST operation to change any of the Object's other headers such as Content-Type, ETag, etc."

But it seems like it'd be nice if you could.

In fact more generally it seems practical to allow for the end user to
update SOME of the header values sent in the response without having to
re-upload the file.  (e.g. Content-Type, Content-Encoding, Expires,
etc.)

Perhaps we define a convention that allows the user to POST "magic
X-Override" keys, which are saved in the .meta file - and appended to
the header of the response, overriding allowed header fields, and
excluding those which we've disallowed.

e.g.
"X-Override-Content-Type"

** Affects: swift
     Importance: Wishlist
         Status: Opinion

-- 
can't change content-type with-out reupload
https://bugs.launchpad.net/bugs/614057
You received this bug notification because you are a member of Registry
Administrators, which is subscribed to OpenStack Object Storage (swift).