In the Local development environment (NGINX), often encountered this situation: debugging JS when the browser is always not loaded with the modified JS content, and directly spit out the last cached code.I have tried the following:Ctrl+f5Ctrl+f5+f5+f5+f5+f5+f5
Service Nginx RestartService nginx stop ... service nginx start
Service php-fpm RestartService php-fpm stop ... service php-fpm start
rebootin Nginx configuration Riga expires-1;in Nginx configuration riga add_header Cache-control ' No-store ';have failed. in the Google Browser debugging mode found all JS files are clear a water 304 not Modified. Go to search engines to find a solution, and clear the answer to the water: after the URL of JS add time stamp:/static/js/common.js-/static/js/common.js?2015.03.04but in the development of debugging, you can not debug every time you have to change the URL it? Kung Fu is not a conscientious, and finally accidentally in a foreign web site to see a netizen also encountered this problem, and ask oneself answer:added in Nginx configurationif_modified_since off;add_header last-modified ""; After restarting Nginx, you are done! PS: If not yet, remember to modify the contents of JS files, and save, and then refresh.
Debugging in addition to add time stamp on the URL, how to avoid JS, CSS is returned 304 state?
