HTTP 101 Switching Protocols vs 409 Conflict
HTTP 101 (Switching Protocols) is a 1xx Informational response, while 409 (Conflict) is a 4xx Client Error response. 101 indicates that the server understands the Upgrade header field request and indicates which protocol it is switching to. 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 server understands the Upgrade header field request and indicates which protocol it is switching to.
Cuándo lo verás
When upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
Cómo solucionarlo
This is normal behavior during protocol upgrades. Ensure your client supports the target protocol.
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
101 is a 1xx Informational response, while 409 is a 4xx Client Error response.
HTTP 101: The server understands the Upgrade header field request and indicates which protocol it is switching to.
HTTP 409: The request conflicts with the current state of the server. Often due to concurrent modification or business rule violations.
You encounter 101 when when upgrading from HTTP/1.1 to WebSocket, or to HTTP/2.
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 101 (Switching Protocols): This is normal behavior during protocol upgrades. Ensure your client supports the target protocol. For 409 (Conflict): Refresh the resource state, resolve conflicts, and retry. Use ETags for optimistic concurrency.