Incorrect content-type sent on JSON responses

Bug #1545430 reported by Brian Cline
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Swift Authentication
Fix Released
Undecided
Brian Cline

Bug Description

Swauth doesn't currently specify a content type when constructing its swob.Response objects that contain JSON bodies, and as a result, it defaults to a "text/html" content type. It should use the proper content type of "application/json".

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to swauth (master)

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

Changed in swauth:
assignee: nobody → Brian Cline (briancline)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to swauth (master)

Reviewed: https://review.openstack.org/279955
Committed: https://git.openstack.org/cgit/openstack/swauth/commit/?id=556aa156979741292bde78425f413f9dee639b4f
Submitter: Jenkins
Branch: master

commit 556aa156979741292bde78425f413f9dee639b4f
Author: Brian Cline <email address hidden>
Date: Sun Feb 14 04:55:42 2016 -0600

    Use correct content type on JSON responses

    Currently, in cases where swauth returns a JSON document as its body,
    it does not specify a content type, and swob defaults it to text/html.

    This change uses a standard content type of 'application/json' in each
    of these instances, and adjusts the tests accordingly.

    Closes-Bug: #1545430
    APIImpact

    Change-Id: I96d343a87f462811bcefb7d402887f8a570fe6bd

Changed in swauth:
status: In Progress → Fix Released
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.