HTTP 201 Created vs 409 Conflict
HTTP 201 (Created) is a 2xx Success response, while 409 (Conflict) is a 4xx Client Error response. 201 indicates that the request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity. In contrast, 409 means that the request conflicts with the current state of the server. Often due to concurrent modification or business rule violations.
Descripción
The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
Cuándo lo verás
After successfully creating a new user, post, order, or other resource via a REST API.
Cómo solucionarlo
No fix needed. Check the Location header for the URL of the new resource.
Descripción
The request conflicts with the current state of the server. Often due to concurrent modification or business rule violations.
Cuándo lo verás
When trying to create a resource that already exists, or updating a resource that was modified by another request.
Cómo solucionarlo
Refresh the resource state, resolve conflicts, and retry. Use ETags for optimistic concurrency.
Diferencias clave
201 is a 2xx Success response, while 409 is a 4xx Client Error response.
HTTP 201: The request succeeded and a new resource was created. Typically returned after POST or PUT requests that create a new entity.
HTTP 409: The request conflicts with the current state of the server. Often due to concurrent modification or business rule violations.
You encounter 201 when after successfully creating a new user, post, order, or other resource via a REST API.
You encounter 409 when when trying to create a resource that already exists, or updating a resource that was modified by another request.
Cuándo usar cada uno
For 201 (Created): No fix needed. Check the Location header for the URL of the new resource. For 409 (Conflict): Refresh the resource state, resolve conflicts, and retry. Use ETags for optimistic concurrency.