---
title: "HTTP 304 Not Modified — What It Means & How to Fix It"
description: "HTTP 304 Not Modified: The resource has not been modified since the last request. Common causes, fixes and how to monitor it."
url: https://uptrack.app/http/304
---

# HTTP 304 Not Modified

The resource has not been modified since the last request. The server tells the client to use its cached copy instead of downloading the resource again. This saves bandwidth and speeds up page loads.

## What does HTTP 304 mean?

The resource has not been modified since the last request. The server tells the client to use its cached copy instead of downloading the resource again. This saves bandwidth and speeds up page loads.

## Common causes

1. 1  
The client sent a conditional request with If-Modified-Since or If-None-Match headers, and the resource has not changed.
2. 2  
Browser cache is working correctly — the ETag or Last-Modified date matches what the server has.
3. 3  
CDN or reverse proxy validated that the cached version is still current.

## How to fix it

1. 1  
No fix needed — 304 is a performance optimization. It means caching is working correctly and saving bandwidth.
2. 2  
If you need to force a fresh response, clear the browser cache or add a cache-busting query parameter (e.g., ?v=2) to the URL.
3. 3  
If the server always returns 304 even after content changes, check your ETag generation or Last-Modified header logic. Stale ETags cause users to see outdated content.

## Monitor for HTTP 304 errors

Uptrack sends fresh requests without cache headers, so your endpoints return full responses (200) rather than 304. This ensures Uptrack validates the actual content, not just the cache layer.

## Catch HTTP errors before your users do

Start free, or choose a plan, for 30-second monitoring and alert confirmation.

[See plans](https://uptrack.app/pricing)

from $3/mo · 30-day money-back guarantee

## Other HTTP status codes

- [HTTP 302 Found](https://uptrack.app/http/302)
- [HTTP 301 Moved Permanently](https://uptrack.app/http/301)
- [HTTP 400 Bad Request](https://uptrack.app/http/400)
- [HTTP 401 Unauthorized](https://uptrack.app/http/401)
- [HTTP 403 Forbidden](https://uptrack.app/http/403)
- [HTTP 204 No Content](https://uptrack.app/http/204)
- [HTTP 404 Not Found](https://uptrack.app/http/404)
- [HTTP 405 Method Not Allowed](https://uptrack.app/http/405)
- [HTTP 201 Created](https://uptrack.app/http/201)
- [HTTP 200 OK](https://uptrack.app/http/200)
- [HTTP 408 Request Timeout](https://uptrack.app/http/408)
- [HTTP 409 Conflict](https://uptrack.app/http/409)
- [HTTP 410 Gone](https://uptrack.app/http/410)
- [HTTP 413 Payload Too Large](https://uptrack.app/http/413)
- [HTTP 415 Unsupported Media Type](https://uptrack.app/http/415)
- [HTTP 422 Unprocessable Entity](https://uptrack.app/http/422)
- [HTTP 429 Too Many Requests](https://uptrack.app/http/429)
- [HTTP 451 Unavailable For Legal Reasons](https://uptrack.app/http/451)
- [HTTP 500 Internal Server Error](https://uptrack.app/http/500)
- [HTTP 502 Bad Gateway](https://uptrack.app/http/502)
- [HTTP 503 Service Unavailable](https://uptrack.app/http/503)
- [HTTP 504 Gateway Timeout](https://uptrack.app/http/504)
- [HTTP 520 Web Server Returns Unknown Error](https://uptrack.app/http/520)
- [HTTP 522 Connection Timed Out](https://uptrack.app/http/522)
