Doublecheck cache control headers for dataset and annotation info request

[philippotto]

If I see it correctly, the dataset info request doesn't have cache control response headers. Browsers might do heuristic caching in that case which could lead to annoying cache problems (see context). Quoting MDN:

Heuristic caching is a workaround that came before Cache-Control support became widely adopted, and basically all responses should explicitly specify a Cache-Control header.

[fm3]

Do you think Cache-Control: no-cache is the right call here? I guess those two requests are not sent by the thousands for one user so refetching it always may be the safest variant while not being too annoying. I wonder if there are any GET routes where we would prefer the heuristic caching?

[philippotto]

Do you think Cache-Control: no-cache is the right call here? I guess those two requests are not sent by the thousands for one user so refetching it always may be the safest variant while not being too annoying.

Yes, I think, Cache-Control: no-cache makes most sense for the info requests.

I wonder if there are any GET routes where we would prefer the heuristic caching?

Hm, apart from static assets (such as images), no GET routes come to my mind which should be explicitly cached in my opinion.