Closed waiylkarim closed 8 years ago
It should be setting the correct etag
headers to make sure it busts the cache on every render. If the etag matches the hash of the content, munee returns a 304. If the etag has changed, then it should return the new content. Can you open up your network panel to see if that is happening? Check to see if your request headers include a If-None-Match
entry.
If you need more information on how caching works in the browser, have a read of this article: https://devcenter.heroku.com/articles/increasing-application-performance-with-http-cache-headers
Closing this out. If you are still having issues, please re-open :).
At first impression it doesn't compile the assets, I have to refresh the page twice in order for it to work!