Http 422 is a valid response code

Bug #1532704 reported by HouMing Wang
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
WSME
New
Undecided
Unassigned

Bug Description

HTTP 422 is valid Status Code Extensions to HTTP/1.1 for webdav[1]. And wsme/pecan consumer will produce this 422 status code, for example, Kubernetes API will returned 422 to Magnum in some failure conditions[2] [3]. We should make 422 a valid code, to prevent the original client error 422 turn into inappropriate server error 500.

[1] http://www.webdav.org/specs/rfc2518.html#status.code.extensions.to.http11
[2] https://github.com/kubernetes/kubernetes/blob/master/pkg/api/errors/errors.go#L32
[3] https://github.com/kubernetes/kubernetes/blob/master/docs/devel/api-conventions.md

Changed in wsme:
assignee: nobody → HouMing Wang (houming-wang)
description: updated
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to wsme (master)

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

Changed in wsme:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on wsme (master)

Change abandoned by HouMing Wang (<email address hidden>) on branch: master
Review: https://review.openstack.org/265724

Changed in wsme:
status: In Progress → New
assignee: HouMing Wang (houming-wang) → nobody
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.