[openstack-dev] [all] HTTP REST API error status code for out of quota errors

Dolph Mathews dolph.mathews at gmail.com
Tue Jun 3 01:26:30 UTC 2014


On Mon, Jun 2, 2014 at 7:21 PM, Christopher Yeoh <cbkyeoh at gmail.com> wrote:

> Hi,
>
> There's been a few patches like this floating around recently which fix
> the incorrect use of 413 as the http error code when a request fails
> because of the requestor is out of quota.
>
> https://review.openstack.org/#/c/95671/
>
> Now 413 is definitely wrong, but sometimes the change is made to 400 or
> 403. Having had a look around at different REST APIs (non openstack) out
> there, 403 does seem to be the most popular choice.
>
>
400 is wrong as well: "The request could not be understood by the server
due to malformed syntax." In this case, the syntax is fine, it's the
requested action that the server is rejecting.

+1 for 403


> Its not totally clear from the rfc (http://www.ietf.org/rfc/rfc2616.txt)
> what it should be, but 403 to me does seem to the most appropriate, and
> whilst its not a big thing I think we should at least be consistent about
> this across all our openstack REST APIs.
>
> Anyone have any objections to this?
>
> Regards,
>
> Chris
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140602/50e05687/attachment.html>


More information about the OpenStack-dev mailing list