HTTP Status Codes
HTTP 409 Conflict
Conflict
What 409 Means
The 409 error on the HTTP Status Codes indicates conflict. This typically occurs due to concurrent edit collision.
A 409 error happens when a request fundamentally conflicts with the current state of the target resource.
Technical Background
The 409 status signals that the server understood the request, but the action would violate business logic or database constraints if executed.
Unlike 400 Bad Request, a 409 request is perfectly formatted, it just clashes with existing data.
Common Causes
- Concurrent edit collision
- Trying to create a resource that already exists
- Database unique constraint violation
Typical Scenarios
- Two administrators try to update the exact same file simultaneously.
- A user tries to register an account with an email address that is already firmly taken.
What to Know
Synchronization of the client with the latest server state or modification of the conflicting payload (e.g., choosing a unique username) resolves the collision.
Frequently Asked Questions
Common questions about HTTP 409 error
It means your request clashes with data already on the server, like trying to create a user that already exists.