The DevOps Drop
Home / Encyclopedia / HTTP Status Codes / 3xx Redirection Responses / 304 Not Modified

304 Not Modified

The HTTP 304 Not Modified status code tells clients that a cached resource is still valid and does not need to be downloaded again.

Published 16 Jul 2026 · HTTP Status Code

What is HTTP 304 Not Modified?

The 304 Not Modified response indicates that a cached version of a resource can still be used.

It improves performance by avoiding unnecessary data transfers.

How It Works

Clients send conditional requests using headers such as:

If-None-Match
If-Modified-Since

If the resource has not changed, the server responds:

HTTP/1.1 304 Not Modified

Common Uses

  • Browser caching
  • CDNs
  • Static assets
  • API caching

Why Does It Matter For DevOps?

304 responses are important when optimising performance and troubleshooting caching behaviour.

  • Reverse proxies
  • Web servers
  • CDN configuration
  • Cache invalidation

Summary

The 304 Not Modified response allows clients to reuse cached resources efficiently.