HUE-347: Ensure CSS files are not cached

Review Request #1350 — Created Dec. 21, 2010 and submitted

shawn
old-hue-rw
HUE-347
hue
marcus, Thomas
commit a7dc525dad0aa856770766467e6383b2cd110228
Author: Shawn Van Ittersum <shawn@cloudera.com>
Date:   Fri Dec 17 14:50:14 2010 -0800

    HUE-347. Ensure CSS files are not cached

:100644 100644 2757710... 9a83c94... M	desktop/core/static/js/Source/CCS/CCS.Desktop.js
Safari only
philip
  1. Why do we want to avoid caching here?  Is this a dev-only usefulness?
    
    (The technologically intense way to avoid caching is to use content-based URLs, but that might be a lot of work.)
    1. we did all sorts of things here; restarted the browser, cleared cache, etc. the changes we made to the css wouldn't show up no matter what. I agree that content-based urls (app.css?version=1) are ideal, but without that dev, making the browser always fetch them is the next best thing...
    2. note that we do the same thing with all our JS and Ajax requests...
  2. 
      
Thomas
  1. Ideally I'd like this to be enabled only in DEV mode or whatever, but this should be OK in the meantime.
    
    Can you create a ticket to expose DEV mode from Django into JS? Should be simple enough, then we can cue off that flag to enable stuff like this in the future.
  2. 
      
Loading...