304 Not Modified
The HTTP status answering a conditional GET to say the copy the client already has is still current, so no body is sent.
In more detail
A client sends its ETag in If-None-Match; if it still matches, the server replies 304 with the validator and caching headers but no body. It is neither an error nor a redirect: it saves the bytes of the body, not the round trip.
Related terms
- ETag — A response header holding an opaque tag that names one exact version of a representation, such as ETag: "1".
- If-None-Match — The request header that sends back an ETag and asks the server to answer 304 Not Modified if that version is still current.
- conditional request — An HTTP request that the server carries out only if a condition in its headers is true, such as If-None-Match or If-Match.
- cache validation — Asking the server whether a stored response is still current by sending back its validator, such as an ETag, in a conditional request.
Taught in
- HTTP Methods And Status Codes — Modern API Architecture: REST, GraphQL & gRPC
- Caching And Conditional Requests — Modern API Architecture: REST, GraphQL & gRPC
- The Fetch API: Streaming Responses, HTTP Caching And Keepalive — Frontend Architecture & Web Platform