The default cache-control header has a heavily negative impact on my web app. Content is generated dynamically as you navigate through the app. Images are constantly being reused but without cache they involve a delay which is clearly noticeable. This slows down navigation a lot and is not acceptab…

Edit: Actually, checking the page a few minutes after initial deploy, images are flickering again. For some reason, the headers settings in netlify.toml don’t seem to stick for long. I can confirm the same issue with our demo site - currently evaluating Netlify / NetlifyCMS for our company site at…

@MatsLanGoH , we appreciate your thoughts on this. We will update this topic if/when the behavior is corrected. Also, please feel free to “watch” this topic (there is a button below) if you want to receive emails about any updates here. Last but not least, welcome to our community site! …

Has this been solved? I believe this may be what is affecting me here [image] Immutable images. How do I specify paths for all images in directory tree in _headers Support We have a conventional content website that is deployed on netlify. By design, practically all the a…

Hi, @Rangoli-Software . I replied in the topic you linked to above. I believe the issue you are experiencing is unrelated to the 304 status issue. The issue filed for the 304 responses not sending custom headers remains open. It is not resolved at this time. (Again, though, I don’t think it is the …

A fix for this issue would be appreciated. For development purpose, we need to totally disable cache management on server-side, but this “304” behaviour breaks our application :cry: Our configuration: /* Cache-Control: no-cache no-store must-revalidate max-age=0 Thank you

[image] dlecan: /* Cache-Control: no-cache no-store must-revalidate max-age=0 It is much better with , between instructions! This is working great: /* Cache-Control: no-cache, no-store, must-revalidate, max-age=0

Hi, @dlecan . If/when the 304 issue is resolved, we’ll post another update here. (This issue is still open at this time.)

Hey @luke , Any updates on this issue ? Could this be related behaviour I’m seeing in this thread. [image] "Uncaught SyntaxError: Unexpected token <" on new build using gatsby JS Support I’m experiencing some issues with an error that has already been mentioned in this pos…

Sorry, we don’t have an update yet. However, looking at your thread, it does look to be the same 304 issue so you’ll want to keep an eye on this thread. We’ll update this thread once we’ve resolved the issue. Thank you for your patience.

Has this issue been resolved yet? I have the same caching issue on my site . The weird thing is, there weren’t any problems with the cache-control header until a few days ago. When I checked it at least 4 days ago (right after the last build), it definitely worked. The caching issue was discovered…

Netlify ignores cache-control for 304

Support

hrishikesh December 17, 2021, 11:57am 29

Hi @nirazul,

The issue sadly still exists.

(re)setting cache

Topic		Replies	Views
(re)setting cache Support headers	1	556	January 1, 2023
Netlify image cdn showing images as stale and cache control headers not applied Support caching	6	130	August 3, 2024
Netlify Images CDN `Cache-Control` Features netlify-cdn-adn , feature-request	10	698	January 21, 2026
Override Cache-Control index.html Support caching	8	3433	September 15, 2020
How to invalidate headers in the Netlify CDN cache Support deployment , netlify-cdn-adn	1	567	December 14, 2023

Netlify ignores cache-control for 304

Related topics