Reviewed:  https://review.openstack.org/304958
Committed: 
https://git.openstack.org/cgit/openstack/nova/commit/?id=a7019a87ba696509d825c6c6f2220331e4ffb033
Submitter: Jenkins
Branch:    master

commit a7019a87ba696509d825c6c6f2220331e4ffb033
Author: Brandon Irizarry <iz.bran...@yahoo.com>
Date:   Wed Apr 13 05:18:25 2016 +0000

    Changed an HTTP exception to return proper code
    
    POSTing to /servers with a content-type of text/plain
    and a text/plain body results in a response code of 400.
    It should be 415. I found this line in the code that
    appears to handle this singular case and modified
    the HTTP exception used to the correct one. Tests were
    also updated accordingly.
    
    Change-Id: I5fa1fdba56803b2ef63b1efaaeeced6ceb7779d9
    Closes-Bug: 1567977


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1567977

Title:
  POST /servers with incorrect content-type returns 400, should be 415

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) liberty series:
  Confirmed
Status in OpenStack Compute (nova) mitaka series:
  Confirmed

Bug description:
  (master nova april 8, 2016)

  POSTing to /servers with a content-type of text/plain and a text/plain
  body results in a response code of 400. This is incorrect. It should
  be 415: <https://httpstatuses.com/415>

  Here's the gabbi demo:

  - name: post bad content-type
    xfail: True
    POST: /servers
    request_headers:
        content-type: text/plain
    data: I want a server so badly
    status: 415

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1567977/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to