FWIW, I consider it a bug :)
On Jul 25, 2013, at 3:29 PM, Sean Dague wrote:
> Some new tempest tests have been showing up that push deeper into the Nova
> API, and popping out seem to be a lot of places where we are returning 422
> status codes.
>
> 422 is WebDav reserved code, not in a prope
On Thu, 25 Jul 2013 10:29:47 -0400
Sean Dague wrote:
> Some new tempest tests have been showing up that push deeper into the
> Nova API, and popping out seem to be a lot of places where we are
> returning 422 status codes.
>
> 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC
On 07/25/2013 10:29 AM, Sean Dague wrote:
> Some new tempest tests have been showing up that push deeper into the
> Nova API, and popping out seem to be a lot of places where we are
> returning 422 status codes.
>
> 422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC
> 4918), and a
Just as a data point, we considered these a *bug* in Cinder and fixed them
as I recall.
On Thu, Jul 25, 2013 at 8:29 AM, Sean Dague wrote:
> Some new tempest tests have been showing up that push deeper into the Nova
> API, and popping out seem to be a lot of places where we are returning 422
>
Some new tempest tests have been showing up that push deeper into the
Nova API, and popping out seem to be a lot of places where we are
returning 422 status codes.
422 is WebDav reserved code, not in a proper HTTP spec (WebDAV; RFC
4918), and a lot of the other projects have purged it out of t
