Cannot edit non prefixed headers

[marcus rowell]

Standard HTTP-specific header names such as "content-type", "content-disposition" etc should not have "X-Object-Meta-" added to the header elements when using Cloudfiles.

With 4.3 and 4.3.1, standard HTTP-specific Metadata headers (e.g. "content-disposition" ) are having "X-Object-Meta-" added to the header on editing via the the Metadata tab of the info window.

In 4.2.1 on adding Metadata headers to objects in Cloudfiles the "content-disposition" was added as is. Now with 4.3 and 4.3.1 "X-Object-Meta-" is prefixed to the metadata. Also existing Metadata headers that were visible in earlier versions are not being displayed in the Metadata tab of the info window.

This was tested on Mac OS X 10.8.3 and 10.7.5 with existing bookmarks to Cloudfiles, as well as new connections using the Rackspace US.cyberduckprofile and a new Swift connection.

[dkocher]

For S3, the following headers are not prepended with a metadata prefix and we should possibly implement the same for Swift storage.

            "content-type",
            "content-md5",
            "content-length",
            "content-language",
            "expires",
            "cache-control",
            "content-disposition",
            "content-encoding",
            X-Object-Manifest,
            X-Purge-Email,
            "origin",
            "access-control-allow-origin",
            "access-control-allow-credentials",
            "access-control-expose-headers",
            "access-control-max-age",
            "access-control-allow-methods",
            "access-control-allow-headers",
            "access-control-request-method",
            "access-control-request-headers"

[dkocher]

In r11080.