At times during development, it would be really nice to prevent HTTP 304 responses (in favor of 200\'s), and cause the Connect/Express static middleware to read every r
This solution is just a workaround. You could solve the problem from the browser side by disabling caching in Chrome. This doesn't help you if you need to work on something outside of Chrome, like Safari on iOS.