What 304 means
The client already has an up-to-date copy, so the server doesn’t send the body again. The client should use its cached version.
When servers send it
In reply to a conditional GET or HEAD, one with If-None-Match (an ETag) or If-Modified-Since (a date), when the resource hasn’t changed.
Why you might see it
- The browser revalidating a cached file that hasn’t changed.
Using it as a developer
- A 304 has no body. It should repeat headers such as
ETag,Cache-ControlandVarythat a 200 would have had. - Lots of 304s for static files is fine, but each one is still a round trip. Long
Cache-Control: max-agewith versioned file names avoids them. - If changes aren’t showing up, check your ETags change when the content does.
If you’re visiting a website
- Nothing. It makes pages load faster. If a page looks out of date, a hard refresh (Ctrl+Shift+R, or Cmd+Shift+R on a Mac) fetches it fresh.
Related codes
- 200 OK: The request worked and the response contains the result.
- 412 Precondition Failed: A condition in the request headers, such as If-Match, wasn’t true, so nothing was changed.
- 206 Partial Content: Here is the part of the file you asked for with a Range header.
Where it’s defined
304 Not Modified is defined in RFC 9110, section 15.4.5. It’s a 3xx code, the redirection class: look somewhere else, or use the copy you already have.
Other 3xx codes
301 Moved Permanently · 302 Found · 303 See Other · 307 Temporary Redirect · 308 Permanent Redirect
Or search them all in the HTTP status code list.
Questions people ask
What does HTTP 304 Not Modified mean?
Is a 304 an error?
Why don’t I see 304s in my browser’s network tab?
max-age, the browser doesn’t ask the server at all, and developer tools show it as 200 from cache instead.