HTTP troubleshooting
304 Not Modified
The server indicates the resource has not changed since the client's last request, used with caching headers like ETag or Last-Modified. In simple terms, this guide helps you understand why the response may make a monitor appear unhealthy and what to check before changing your monitor settings.
What 304 means for a monitor
Statixoup records an incident when 304 does not match the monitor's expected status code. Confirm the response before changing monitor rules.
Troubleshooting checklist
- 1.
Check 1
Confirm caching headers such as ETag or Last-Modified are configured correctly.
- 2.
Check 2
Ensure your monitor requests do not include cache-busting headers unless needed.
- 3.
Check 3
If monitoring content freshness, consider requesting headers that bypass caches.
After the service is fixed
- Confirm the URL returns the expected status without a browser session.
- Review response-time and incident history for the recovery.
- Change Expected status code only when the different response is intentional.
Avoid hiding a real outage
Changing the expected code can make an unhealthy response appear operational. Fix the service first whenever the response is unexpected.