DELETE /servers returns 404 when it should return 405
Bug #1567970 reported by
Chris Dent
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Confirmed
|
Low
|
Unassigned |
Bug Description
(Master devstack, master nova, April 8, 2016)
curl -v -H 'x-auth-token: e893759204ff41d
returns an HTTP status code of 404. It should be 405: <https:/
This is because /servers is in fact a valid URL, you can call at least GET and POST on it.
gabbi version:
- name: try bad method
desc:
xfail: True
DELETE: /servers
status: 405
Changed in nova: | |
status: | New → Confirmed |
importance: | Undecided → Low |
tags: | added: gabbi |
Changed in nova: | |
assignee: | nobody → Gregory Hooks (gregoryhooksjr) |
Changed in nova: | |
status: | In Progress → Confirmed |
assignee: | Gregory Hooks (gregoryhooksjr) → nobody |
Changed in nova: | |
assignee: | nobody → stgleb (gstepanov) |
status: | Confirmed → In Progress |
To post a comment you must log in.
I have been able to re-produce this bug. It appears that any HTTP method other than GET or POST will return a status code of 404. I am currently in the process of finding out why other HTTP methods are not being properly handled.