对于自定义错误，应使用什么HTTP状态代码? [英] What HTTP status code should I use for custom errors?

问题描述

我需要返回有关以下错误的信息:客户的联系人不能超过3个，现场工作为空，超出了个操作限制.

I need to return information about errors like: customer can't have more than 3 contacts, field Job is empty, limit of operations was exceeded.

我需要用自己的状态代码发送每个错误吗?
我可以对所有这些错误使用 400 BadRequest 吗?

Do I need send each error with own status code?
Can I use 400 BadRequest for all those errors?

推荐答案

我可以对所有这些错误使用400 BadRequest吗?

Can I use 400 BadRequest for all those errors?

当然可以.

这曾经有点可疑，因为RFC 2616将400错误请求定义为:

This used to be a bit questionable, because RFC 2616 defined 400 Bad Request as:

由于格式错误，服务器无法理解该请求句法.客户应在没有以下情况的情况下不重复请求修改.

The request could not be understood by the server due to malformed syntax. The client SHOULD NOT repeat the request without modifications.

但是，通常没有更适用的更好状态，因此通常被用作最合适的状态.

However, there often wasn't a more applicable better status, so it was often used as the best-fit.

随着RFC 7231淘汰了RFC 2616并为400提供了更广泛的定义，这种情况已经改变:

This has changed with RFC 7231 obsoleting RFC 2616 and giving a broader definition to 400:

400(错误请求)状态代码表示服务器无法执行以下操作:由于某些原因，将不会处理该请求客户端错误(例如，格式错误的请求语法，无效的请求邮件框架或欺骗性请求路由).

The 400 (Bad Request) status code indicates that the server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing).

由于被认为是客户错误的事情"涵盖了许多罪过，因此现在更加明确地适用.

Because "something that is perceived to be a client error" covers a multitude of sins, it's now more explicitly applicable.

当然，如果另一个4xx代码确实匹配得更好(例如，与不存在的内容相关的请求的404(消息中的ID找不到匹配项))，那么它是更好的选择.

Of course, if another 4xx code does match better (e.g. 404 for a request that relates to something that doesn't exist [an ID in the message doesn't find a match]), then it is the better option.

这篇关于对于自定义错误，应使用什么HTTP状态代码?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！