How to prevent "304 Not Modified" in nginx?

header nginx http-status-code-304
Moon picture Moon · Oct 5, 2011 · Viewed 26k times · Source

I'm trying to disable all the caches in nginx for testing purpose.

I've set the following line

add_header Cache-Control no-cache;

I see that the page itself is not cached, but the images, css, and javascripts are. I suspect that this is because Firefox is getting "304 Not Modified" header.

Is there a way to prevent it?

P.S:

I think I found it myself. Firefox shows '200 OK' all the time now.

Is this correct way?

I've added

if_modified_since off;
add_header Last-Modified "";

Answer

Juan-José Del Río Holgado picture Juan-José Del Río Holgado · Oct 5, 2011

Sounds right to me.

If the agent (in this case Firefox) says 200 OK, it means the transfer happened.

Related questions

Upstream too big - nginx + codeigniter

I am getting this error from Nginx, but can't seem to figure it out! I am using codeigniter and am using the database for sessions. So I'm wondering how the header can ever be too big. Is there anyway to …

Read More
Modifying a Location header with nginx proxy_pass

I have an nginx proxy_pass setup to pass every request on /api through to a backend Tomcat REST service. This service in some cases returns a Location header which varies according to the type of request, e.g., Location: …

Read More
How to fix "Headers already sent" error in PHP

When running my script, I am getting several errors like this: Warning: Cannot modify header information - headers already sent by (output started at /some/file.php:12) in /some/file.php on line 23 The lines mentioned in the error messages …

Read More