Glance v2: HTTP 404s are returned for unallowed methods
Bug #1297362 reported by
Alex Meade
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Low
|
Kent Wang |
Bug Description
Requests for many resources in Glance v2 will return a 404 if the request is using an unsupported HTTP verb for that resource. For example, the /v2/images resource does exist but a 404 is returned when attempting a DELETE on that resource. Instead, this should return an HTTP 405 MethodNotAllowed response.
Changed in glance: | |
assignee: | nobody → Kent Wang (k.wang) |
Changed in glance: | |
status: | New → In Progress |
Changed in glance: | |
status: | In Progress → Fix Committed |
Changed in glance: | |
milestone: | none → juno-2 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | none → juno-3 |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | juno-3 → 2014.2 |
To post a comment you must log in.
According to http:// www.restapituto rial.com/ lessons/ httpmethods. html
it is perfectly RESTful to return 404 when attempting to DELETE the entire collection (e.g. /v2/images)
But for other lesser used operations (OPTIONS, HEAD), maybe we still can return a 405? or a 501 (method not implemented)?