Allan Tatter
Allan Tatter
Maybe a more scalable solution would be to add the maximum levels of nestability? In your case you would set it either 0 or 1.
Probably not yet but our team will in the near future consider adding this functionality. Better yet, if you would leave us a PR.
Unfortunately I did not find the reason why GCP Cloud CDN behaves like that in their documentation: * https://cloud.google.com/cdn/docs/serving-stale-content * https://cloud.google.com/cdn/docs/caching#expiration However, that would not be the only reason why...
@StrangePeanut What are you talking about? :D > Wouldn't off stop NGINX from sending headers at all basically letting the browser decide what to do? Nope, `off` means that it...
I agree that breaking changes should not be merged hastily. Although bugs should be fixed. So it depends whether we think this is a bug or just one way it...
@jchimene So you think it's the expected behaviour that you see on my graph? I don't think it's rare case that the backend frameworks add `Cache-Control` headers into the response.
@StrangePeanut I like your proposed solution, at least it fixes the initial issue. And if I need to add dynamic `Cache-Control` headers then I can do that by adding custom...
`expires epoch` could be a better option, agreed. Will make that change.
@LeoColomb Done. However won't the test fail now as you changed the expected result of `Cache-Control` from `max-age=0` to not being there instead of `no-cache`?
What is the alternative? Not using anything or is it closed source?