swift client does not allow content type to be specified

[Tong Li]

Currently the swift client does not allow specify content type when upload an object. In many cases the client code guess it wrong.
There needs to be an option to allow client to specify content type during the upload of an object

[Ryan Goltry (ryan-goltry)]

When uploading binary files using the swift client, the content type is being detected as application/octet-stream. For large files, 5 GB and above, this has a very negative impact on the download speed since it is pulled with a base64 encoding bloating the network traffic. Being able to set the content-type at upload time with the swift client would address this.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/24474

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/24474
Committed: http://github.com/openstack/python-swiftclient/commit/48f446a93883fc615d23ac1148fd4b082aed9c86
Submitter: Jenkins
Branch: master

commit 48f446a93883fc615d23ac1148fd4b082aed9c86
Author: tong li <email address hidden>
Date: Mon Mar 18 09:47:59 2013 -0400

    Allow user to specify headers at the command line.

    Currently swift client does not allow content type to be specified
    when upload an object. It does not allow a user to change content
    type neither. This patch will allow a user to specify content
    type by using upload command or modify the content type by using
    post command.

    For example:
    1. To upload an object with specific content type:
    swift upload -H content-type:applicaiton/xml con1 file1

    2. To modify an object to a specific content type:
    swift post -H content-type:application/josn con1 file1

    This patch also allow a client to specify other request headers.

    Change-Id: I12db83a1d465285e0906889cc67dfaa44e059568
    Fixes: bug #1154621