In addition to adding a timestamp to the URL during debugging, how to prevent js and css from returning a 304 status? _html/css_WEB-ITnose

In the local development environment (nginx), we often encounter this situation: when debugging js, the browser always does not load the modified js content, but directly spits out the last cached code.

I have tried the following:

ctrl F5

ctrl F5 F5 F5 F5 F5 F5

service nginx restart

service nginx stop ... service nginx start

service php-fpm restart

service php-fpm stop ... service php -fpm start

reboot

Add expires -1 in nginx configuration;

Add add_header Cache-Control 'no-store';

in nginx configuration All failed.

In the debugging mode of Google Chrome, it was found that all js files were all 304 Not Modified. Then I searched for a solution in the search engine, and found another clear answer: add a timestamp after the js URL:

/static/js/common.js -> /static/js/common. js?2015.03.04

But in development and debugging, you can’t change the URL every time you debug, right?

The hard work paid off, and finally I accidentally saw a netizen on a foreign website who also encountered this problem, and asked and answered himself:

Add

if_modified_since off;

add_header Last-Modified "";

After restarting nginx, you're done!

ps: If it still doesn’t work, remember to modify the content of the js file first, save it, and then refresh it.