assetURL should not generate cache headers when in dev mode


#1

Hey

We run necessary tasks in continuous mode while developing to avoid running enonic project deploy after a change.
But the problem is that assetUrl to css-file contains build id, then we have to run enonic project deploy to see changes in css.
If assetUrl did not generated build id in dev mode, the problem would have been resolved

Carina :slight_smile:


#2

Hey again, suddenly it works. I think the whole problem was browser caching :smile:


#3

Are you saying assets already donโ€™t have cache headers when in dev mode?


#4

To me, it looks like the headers are still instructing the browser to cache, even in dev mode.
Iโ€™ve added it to backlog. Will be a nice improvent.


#5

It have cache header, but when disabling cache in chrome i got the changes in css :slight_smile: But nice improment to remove cache header in devmode anyway :grinning:


#6

Will be fixed in 7.4.


#7