Nova Metadata Service was not setting the Content-Type
in the HTTP Response headers. Because of this, clients
were receiving the default Content-Type which is "text/html".
The changes done in this patch will include proper Content-Type
in the HTTP response headers.
Reviewed: https:/ /review. openstack. org/76112 /git.openstack. org/cgit/ openstack/ nova/commit/ ?id=cae7a46df0d b8fe2fad06f5c74 3807cee948af68
Committed: https:/
Submitter: Jenkins
Branch: master
commit cae7a46df0db8fe 2fad06f5c743807 cee948af68
Author: sridhargaddam <email address hidden>
Date: Tue Feb 25 13:20:19 2014 +0530
Include proper Content-Type in the HTTP Headers
Nova Metadata Service was not setting the Content-Type
in the HTTP Response headers. Because of this, clients
were receiving the default Content-Type which is "text/html".
The changes done in this patch will include proper Content-Type
in the HTTP response headers.
Closes-Bug: #1243878 63d7f44f93835c6 06d679a7ab3
Change-Id: Ia65cdf8099c85f