Hi, thanks for your reply. Yes, I realized that Javascript and CSS assets are served correctly. So what I realize is the actual issue is that assets served via Netlify Large Media (i.e. images on my site, which are also served under the /_app/assets/ folder with a hash in URL, thanks to ViteJS) don’t respect the header rules, and set their own cache policy.
So if you go to /eshop/, there’s a lot of images, and all of them have cache-control: public, max-age=0, must-revalidate. Nice way to verify it is to let the page load for first time, and then refresh the page (make sure your devtools don’t disable cache). This is what I see:
The 304s are images - they were previously loaded with the above cache-control: [...],must-revalidate, while the 200 OK 0 ms responses are those assets loaded as immutable. Sorry for not investigating properly, and by searching forums I see that this is a known issue. Thanks for your help with rubber-ducking 