content-type for unauthorized requests is set incorrectly

Bug #745138 reported by Brian Lamar
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
In Progress
Undecided
Brian Lamar

Bug Description

curl -v -H "Accept: application/xml" http://172.19.0.3:8774/v1.0
* About to connect() to 172.19.0.3 port 8774 (#0)
* Trying 172.19.0.3... connected
* Connected to 172.19.0.3 (172.19.0.3) port 8774 (#0)
> GET /v1.0 HTTP/1.1
> User-Agent: curl/7.21.0 (x86_64-pc-linux-gnu) libcurl/7.21.0 OpenSSL/0.9.8o zlib/1.2.3.4 libidn/1.18
> Host: 172.19.0.3:8774
> Accept: application/xml
>
< HTTP/1.1 401 Unauthorized
< Content-Type: text/html; charset=UTF-8
< Content-Length: 316
< Date: Tue, 29 Mar 2011 17:44:38 GMT
<
<unauthorized code="401">
    <message>
        This server could not verify that you are authorized to
access the document you requested. Either you supplied the
wrong credentials (e.g., bad password), or your browser
does not understand how to supply the credentials required.

    </message>
</unauthorized>
* Connection #0 to host 172.19.0.3 left intact
* Closing connection #0

As you can see above, the Content-Type is "text/html" when it should be "application/xml".

Brian Lamar (blamar)
Changed in nova:
status: New → In Progress
assignee: nobody → Brian Lamar (blamar)
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.