[Solved] A client sends a request with header If-None-Match: "xyz789". The server responds with:HTTP/1.1 200 OK ETag: "abc123" { "data": "new content" }What is the likely problem in this interaction? | Rest API

Rest API - Caching Strategies

A client sends a request with header If-None-Match: "xyz789". The server responds with:

HTTP/1.1 200 OK
ETag: "abc123"
{ "data": "new content" }

What is the likely problem in this interaction?

AThe server sent a different ETag, indicating data changed, so 200 OK is correct

BThe server should respond with 304 Not Modified instead of 200 OK

CThe client sent an invalid ETag header

DThe server response is missing the If-None-Match header

Step-by-Step Solution

Solution:

Step 1: Compare client and server ETags
Client sent "xyz789", server responded with "abc123" which is different.
Step 2: Understand server response code
Since ETags differ, data changed, so server correctly sends 200 OK with new data.
Final Answer:
The server sent a different ETag, indicating data changed, so 200 OK is correct -> Option A
Quick Check:
Different ETag means data changed, send 200 OK [OK]

Quick Trick: Different ETag means new data, so 200 OK is correct [OK]

Common Mistakes:

MISTAKES

Master "Caching Strategies" in Rest API

9 interactive learning modes - each teaches the same concept differently

More Rest API Quizzes

A client sends a request with header If-None-Match: "xyz789". The server responds with: