HTTP 304 Not Modified — What It Means

What HTTP status code 304 Not Modified means, when servers return it, and how to handle it correctly.

Published September 23, 2026

HTTP 304 Not Modified tells the client its cached copy is still valid, so no body is sent. It saves bandwidth by answering conditional requests that use If-None-Match or If-Modified-Since.

What it means

The server compares the client's ETag or date with the current version; if they match, it replies 304 with no body.

Common causes: Browser revalidating cached files; CDN revalidation; Conditional API requests.

On the wire

GET /app.css HTTP/1.1
HTTP/1.1 304 Not Modified
If-None-Match: "abc123"
ETag: "abc123"
A typical 304 exchange.

Practical examples

Test it from the shell

curl -i https://example.com/path   # look for HTTP 304

Handling 304 in code or config

app.use(express.static('public', { etag: true }))

How to fix it

Send ETag or Last-Modified headers; Do not include a body; Check cache headers if you never see 304.

1. Reproduce: curl -i <url>
2. Confirm the status is 304
3. Apply the fix above and re-test

Common mistakes

  • Treating this as an error when it is a normal part of HTTP.
  • Do not include a body
  • Ignoring the response headers that explain the details.

Key takeaways

  • 304 means Not Modified.
  • HTTP 304 Not Modified tells the client its cached copy is still valid, so no body is sent.
  • Read the response headers and logs for the exact cause.

FAQ

Is 304 an error?

No, it is an efficient success for cached content.

Is 304 a client or server error?

It is a redirection status code, in the 3xx class.

More HTTP articles