另一个潜在的治疗方法是使用PATCH。PATCH被定义为改变内部状态的东西，不局限于追加。

PATCH将通过允许您更新已经存在的项目来解决这个问题。参见:RFC 5789: PATCH

也许是在游戏后期，但我在尝试创建REST API时偶然发现了这个语义问题。

为了稍微扩展一下wrkken的回答，我认为您可以根据情况使用409 Conflict或403 Forbidden -简而言之，当用户完全无法解决冲突并完成请求时使用403错误(例如，他们不能发送DELETE请求来显式删除资源)，或者如果可能做一些事情，则使用409。

10.4.4禁止403 服务器理解请求，但拒绝执行。 授权没有帮助，请求不应该重复。如果 请求方法不是HEAD，服务器希望公开 为什么要求没有被满足，它应该描述原因 对于实体中的拒绝。如果服务器不希望做出 此信息可用于客户端，状态代码404(不是 Found)可以代替。

现在，有人说“403”，就会想到权限或身份验证问题，但规范说，这基本上是服务器告诉客户端它不会这样做，不要再问了，这就是客户端不应该这样做的原因。

至于PUT vs. POST…当用户没有办法或不应该为资源创建标识符时，POST应该用于创建资源的新实例。当资源的标识已知时，使用PUT。

9.6 PUT ... The fundamental difference between the POST and PUT requests is reflected in the different meaning of the Request-URI. The URI in a POST request identifies the resource that will handle the enclosed entity. That resource might be a data-accepting process, a gateway to some other protocol, or a separate entity that accepts annotations. In contrast, the URI in a PUT request identifies the entity enclosed with the request -- the user agent knows what URI is intended and the server MUST NOT attempt to apply the request to some other resource. If the server desires that the request be applied to a different URI, it MUST send a 301 (Moved Permanently) response; the user agent MAY then make its own decision regarding whether or not to redirect the request.

另一个潜在的治疗方法是使用PATCH。PATCH被定义为改变内部状态的东西，不局限于追加。

PATCH将通过允许您更新已经存在的项目来解决这个问题。参见:RFC 5789: PATCH

I think for REST, you just have to make a decision on the behavior for that particular system in which case, I think the "right" answer would be one of a couple answers given here. If you want the request to stop and behave as if the client made a mistake that it needs to fix before continuing, then use 409. If the conflict really isn't that important and want to keep the request going, then respond by redirecting the client to the entity that was found. I think proper REST APIs should be redirecting (or at least providing the location header) to the GET endpoint for that resource following a POST anyway, so this behavior would give a consistent experience.

EDIT: It's also worth noting that you should consider a PUT since you're providing the ID. Then the behavior is simple: "I don't care what's there right now, put this thing there." Meaning, if nothing is there, it'll be created; if something is there it'll be replaced. I think a POST is more appropriate when the server manages that ID. Separating the two concepts basically tells you how to deal with it (i.e. PUT is idempotent so it should always work so long as the payload validates, POST always creates, so if there is a collision of IDs, then a 409 would describe that conflict).

在阅读了这篇文章和其他几篇关于状态码使用的长达数年的讨论之后，我得出的主要结论是，必须仔细阅读规范，重点关注正在使用的术语、它们的定义、关系和周围的上下文。

相反，从不同的答案中可以看出，经常发生的情况是，部分规范被剥离了上下文，并基于感觉和假设进行孤立的解释。

这将是一个相当长的回答，简短的总结是，HTTP 409是报告“添加新资源”操作失败的最合适的状态代码，如果具有相同标识符的资源已经存在。以下是对原因的解释，完全基于权威来源- RFC 7231中所述。

那么，在OP的问题中描述的情况下，为什么409冲突是最合适的状态代码?

RFC 7231对409冲突状态码的描述如下:

409(冲突)状态代码表示由于与目标资源的当前状态冲突而无法完成请求。

这里的关键组件是目标资源及其状态。

目标资源

RFC 7231对该资源的定义如下:

HTTP请求的目标称为“资源”。HTTP不限制资源的性质;它仅仅定义了一个可能用于与资源交互的接口。每个资源由统一资源标识符(Uniform resource Identifier, URI)标识，如[RFC7230]章节2.7所述。

因此，当使用HTTP接口时，我们总是通过对uri应用HTTP方法来操作由uri标识的资源。

当我们打算添加一个新资源时，基于OP的例子，我们可以:

在资源/objects/{id}中使用PUT; 对资源/对象使用POST。

/objects/{id}无关紧要，因为在使用PUT方法时不可能有冲突:

PUT方法请求用请求消息有效负载中包含的表示所定义的状态创建或替换目标资源的状态。

如果具有相同标识符的资源已经存在，它将被PUT替换。

我们将关注/objects资源和POST。

RFC 7231对POST说:

POST方法要求目标资源根据资源自己的特定语义处理请求中包含的表示。例如，POST用于以下函数(以及其他函数):…3)创建一个尚未被源服务器识别的新资源;4)将数据追加到资源的现有表示中。

与OP对POST方法的理解相反:

由于POST的意思是“追加”操作…

将数据追加到资源的现有表示只是可能的POST“函数”之一。此外，OP在提供的例子中实际上所做的不是直接将数据追加到/objects表示中，而是创建一个新的独立资源/objects/{id}，然后它成为/objects表示的一部分。但这并不重要。

重要的是资源表示的概念，它把我们带到了……

资源状态

RFC 7231解释说:

考虑到资源可以是任何东西，并且HTTP提供的统一接口类似于一个窗口，通过该窗口，人们只能通过将消息传递给另一端的某个独立参与者来观察并对该事物采取行动，因此需要一个抽象来表示(“代替”)我们通信中该事物的当前或期望状态。这种抽象称为表示[REST]。

对于HTTP的目的，“表示”是旨在反映给定资源的过去、当前或期望状态的信息，其格式可以通过协议轻松通信，并由一组表示元数据和潜在的无限表示数据流组成。

这还不是全部，规范继续描述表示部分——元数据和数据，但是我们可以总结出，由元数据(报头)和数据(有效负载)组成的资源表示反映了资源的状态。

现在，我们了解了409冲突状态代码的用法所需的两个部分。

409年冲突

让我们重申:

409(冲突)状态代码表示由于与目标资源的当前状态冲突而无法完成请求。

那么它是如何合适的呢?

We POST to /objects => our target resource is /objects. OP does not describe the /objects resource, but the example looks like a common scenario where /objects is a resource collection, containing all individual "object" resources. That is, the state of the /objects resource includes the knowledge about all existing /object/{id} resources. When the /objects resource processes a POST request it has to a) create a new /object/{id} resource from the data passed in the request payload; b) modify its own state by adding the data about the newly created resource. When a resource to be created has a duplicate identifier, that is a resource with the same /object/{id} URI already exists, the /objects resource will fail to process the POST request, because its state already includes the duplicate /object/{id} URI in it.

这正是409冲突状态代码描述中提到的与目标资源当前状态的冲突。

我会选择422不可处理实体，当请求无效时使用，但问题不在于语法或身份验证。

作为反对其他答案的论据，使用任何非4xx错误代码将暗示它不是客户端错误，而它显然是。使用非4xx错误代码来表示客户端错误完全没有意义。

It seems that 409 Conflict is the most common answer here, but, according to the spec, that implies that the resource already exists and the new data you are applying to it is incompatible with its current state. If you are sending a POST request, with, for example, a username that is already taken, it's not actually conflicting with the target resource, as the target resource (the resource you're trying to create) has not yet been posted. It's an error specifically for version control, when there is a conflict between the version of the resource stored and the version of the resource requested. It's very useful for that purpose, for example when the client has cached an old version of the resource and sends a request based on that incorrect version which would no longer be conditionally valid. "In this case, the response representation would likely contain information useful for merging the differences based on the revision history." The request to create another user with that username is just unprocessable, having nothing to do with any version conflict.

为了记录，422也是GitHub使用的状态码，当您尝试按已使用的名称创建存储库时。