409 Conflict in Rest API

Introduction

The 409 Conflict status code tells the client that the request could not be completed because it conflicts with the current state of the server. It helps avoid problems when two things try to change the same data at the same time.

When two users try to update the same record at the same time.

When a client tries to create a resource that already exists.

When a request would cause a duplicate entry in a database.

When a version conflict happens during data synchronization.

When a request violates a rule that prevents conflicting changes.

Syntax

Rest API

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "error": "Conflict",
  "message": "Description of the conflict"
}

The status code 409 is sent in the HTTP response status line.

The response body usually explains what caused the conflict.

Examples

This response tells the client that the email they tried to use is already taken.

Rest API

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "error": "Conflict",
  "message": "User with this email already exists."
}

This response warns that the document changed since the client last fetched it.

Rest API

HTTP/1.1 409 Conflict
Content-Type: application/json

{
  "error": "Conflict",
  "message": "The document has been modified by another user."
}

Sample Program

This simple Flask app simulates user registration. If the email is already in the 'database', it returns a 409 Conflict with a clear message. Otherwise, it registers the user.

Rest API

from flask import Flask, request, jsonify

app = Flask(__name__)

# Simulated database
users = {"[e-mail]": {"name": "Alice"}}

@app.route('/register', methods=['POST'])
def register():
    data = request.json
    email = data.get('email')
    if email in users:
        return jsonify({"error": "Conflict", "message": "User with this email already exists."}), 409
    users[email] = {"name": data.get('name')}
    return jsonify({"message": "User registered successfully."}), 201

if __name__ == '__main__':
    app.run(debug=True)

Important Notes

Always provide a clear message in the response body to help clients understand the conflict.

Use 409 Conflict to keep data consistent and avoid overwriting important changes.

Summary

409 Conflict means the request cannot be completed due to a conflict with current server data.

It is useful when multiple clients try to change the same data at once.

Always explain the conflict clearly in the response body.

Practice

1. What does the HTTP status code 409 Conflict indicate in a REST API?

easy

A. The request cannot be completed because it conflicts with the current state of the server data.

B. The requested resource was not found on the server.

C. The server encountered an unexpected error while processing the request.

D. The request was successful and a new resource was created.

Solution

1. Step 1: Understand HTTP status codes purpose

   Each HTTP status code has a specific meaning. 409 means conflict with current data.

2. Step 2: Match 409 meaning to options

   The request cannot be completed because it conflicts with the current state of the server data. correctly describes 409 as a conflict preventing request completion.

3. Final Answer:

   The request cannot be completed because it conflicts with the current state of the server data. -> Option A

4. Quick Check:

   409 Conflict = Request conflicts with server data [OK]

Hint: 409 means data conflict stops request completion [OK]

Common Mistakes:

• Confusing 409 with 404 Not Found
• Thinking 409 means server error (500)
• Assuming 409 means success

2. Which of the following is the correct way to respond with a 409 Conflict status in a REST API using HTTP headers?

easy

A. HTTP/1.1 200 OK

B. HTTP/1.1 500 Internal Server Error

C. HTTP/1.1 409 Conflict

D. HTTP/1.1 404 Not Found

Solution

1. Step 1: Identify correct HTTP status line for 409

   The status line must include the code 409 and the phrase 'Conflict'.

2. Step 2: Match status line to options

   HTTP/1.1 409 Conflict correctly shows 'HTTP/1.1 409 Conflict'. Others show wrong codes.

3. Final Answer:

   HTTP/1.1 409 Conflict -> Option C

4. Quick Check:

   409 Conflict status line = HTTP/1.1 409 Conflict [OK]

Hint: 409 Conflict status line must say '409 Conflict' exactly [OK]

Common Mistakes:

• Using 200 OK instead of 409
• Mixing 404 or 500 with 409
• Omitting the status phrase 'Conflict'

3. Consider this REST API response snippet when two clients try to update the same resource simultaneously:

{
  "status": 409,
  "message": "Update conflict: resource has been modified by another client."
}

What is the expected client behavior after receiving this response?

medium

A. Fetch the latest resource state and resolve the conflict before retrying.

B. Ignore the conflict and assume update succeeded.

C. Retry the update immediately without changes.

D. Delete the resource to avoid conflicts.

Solution

1. Step 1: Understand 409 Conflict meaning in concurrent updates

   It means the resource changed since client last fetched it, so update conflicts.

2. Step 2: Determine safe client action

   Client should get latest data, resolve differences, then retry update to avoid overwriting.

3. Final Answer:

   Fetch the latest resource state and resolve the conflict before retrying. -> Option A

4. Quick Check:

   409 Conflict means update conflict; fetch and resolve first [OK]

Hint: On 409, fetch latest data before retrying update [OK]

Common Mistakes:

• Retrying update blindly causing repeated conflicts
• Ignoring the conflict and assuming success
• Deleting resource unnecessarily

4. You have this server code snippet handling updates:

if resource.version != client_version:
    return Response(status=409, body={"error": "Version mismatch"})
else:
    update_resource()

But clients report they get 409 even when no conflict exists. What is the likely bug?

medium

A. Clients are sending wrong HTTP methods.

B. The update_resource() function is missing.

C. The server should return 404 instead of 409.

D. The server is not comparing versions correctly; types may differ causing mismatch.

Solution

1. Step 1: Analyze version comparison logic

   If types differ (e.g., string vs int), equality check fails causing false conflicts.

2. Step 2: Identify likely cause of false 409

   Incorrect type comparison leads to always triggering 409 even if versions match logically.

3. Final Answer:

   The server is not comparing versions correctly; types may differ causing mismatch. -> Option D

4. Quick Check:

   Type mismatch in version check causes false 409 [OK]

Hint: Check data types when comparing versions to avoid false conflicts [OK]

Common Mistakes:

• Assuming missing update function causes 409
• Confusing 409 with 404 errors
• Blaming client HTTP methods without evidence

5. You are designing a REST API for editing documents. To prevent update conflicts, you decide to use the 409 Conflict status. Which approach best uses 409 to handle concurrent edits?

hard

A. Always accept updates and overwrite existing data without checks.

B. Require clients to send a version number with updates; if it doesn't match server's current version, respond with 409 and conflict details.

C. Return 409 whenever a client sends an update, regardless of version.

D. Ignore versioning and rely on client retries without conflict responses.

Solution

1. Step 1: Understand concurrency control with 409

   Using version numbers lets server detect if data changed since client last fetched it.

2. Step 2: Choose approach that uses 409 properly

   Require clients to send a version number with updates; if it doesn't match server's current version, respond with 409 and conflict details. uses version check and returns 409 only on real conflicts with details.

3. Final Answer:

   Require clients to send a version number with updates; if it doesn't match server's current version, respond with 409 and conflict details. -> Option B

4. Quick Check:

   Version check + 409 Conflict = best concurrency control [OK]

Hint: Use version numbers and 409 to handle concurrent edits safely [OK]

Common Mistakes:

• Overwriting data blindly without conflict checks
• Returning 409 for every update request
• Ignoring versioning and conflicts