DevArbor
4xx Client Error

409 Conflict

What it means

The request couldn't be completed because it conflicts with the current state of the resource. This is often used for version control conflicts or duplicate creation attempts. The client should resolve the conflict and retry.

Site Visitor

What can I do?

  • Check the URL for typos — a single wrong character causes most 4xx errors.
  • Try navigating to the site's homepage and searching from there.
  • If the problem persists after retrying, contact the site owner.
Developer

How to debug & fix

  1. Return 409 with details about the conflicting state
  2. Include the conflicting resource in the response so the client can resolve it
  3. Use optimistic locking (ETag + If-Match) to detect edit conflicts
  4. Return the conflicting resource or ETag in the 409 body so the client can merge or resolve.

Code Example

Node.js / Express
app.post('/users', async (req, res) => {
  const exists = await User.findByEmail(req.body.email);
  if (exists) {
    return res.status(409).json({
      error: 'Conflict',
      message: 'A user with this email already exists'
    });
  }
  // create user...
});

Related Status Codes

400 Bad Request 422 Unprocessable Entity

How HTTP Status Codes Work

Every HTTP response carries a three-digit status code that tells the client — browser, API consumer, or search-engine crawler — exactly what happened. The first digit defines the class: 1xx informational (request in progress), 2xx success, 3xx redirection, 4xx client error (bad request, missing auth, not found), and 5xx server failure.

Status codes are standardised in RFC 9110 (HTTP Semantics, 2022). Extensions like WebDAV (RFC 4918) and rate-limit headers (RFC 6585) added codes beyond the core set. When a client receives an unrecognised code, the rule is to treat it as the generic x00 of its class.

Why the Right Code Matters

Semantically correct codes help search engines index accurately (301 passes link equity; 410 removes pages faster than 404), allow API clients to implement correct retry logic (429 + Retry-After, 503 + Retry-After), and let monitoring systems distinguish bugs (500) from load issues (503) from auth failures (401/403).

Looking up a different status code? The full reference covers all HTTP codes with causes, fix guides, and copyable code examples for Node.js and Python.

Browse the full HTTP Status Code reference →

Frequently Asked Questions

What does HTTP 409 Conflict mean?
The request couldn't be completed because it conflicts with the current state of the resource. This is often used for version control conflicts or duplicate creation attempts. The client should resolve the conflict and retry.
Is HTTP 409 the visitor's fault?
HTTP 409 Conflict is generally a client-side error, meaning the request itself has an issue. However, many causes — such as a broken link on the site or a misconfigured redirect — are the website owner's responsibility, not the visitor's.
How do I fix HTTP 409 Conflict?
As a visitor: check the URL for typos, go to the homepage, or search for the content. As a developer: return 409 with details about the conflicting state.