Dynamic pages being cached, could OOD send "no-cache" network headers?

[Micket]

I had some cryptic issues from a users, which turns out to be caused by the batch connect forms containing cached information.
I'm using drop down list populated with some dynamically computed values (different jupyter notebook runtimes), and it had cached some outdated (now nonexistent) options for the user.

A simple F5 and the page is correct, but i think it would be best if these pages would hint to the browsers not to ever cache them, especially since things like auto-populated slurm sacctmgr information can change and such.

I'm a bit outside my expertise, but i found that OOD sends:
Cache-Control: max-age=0, private, must-revalidate
for these pages, and comparing with another site that has lost of dynamically generated material it sends
Cache-Control: max-age=0, no-cache, no-store, must-revalidate, private
so perhaps these form pages should be also be sending the no-cache, no-store network headers on pages with forms?

┆Issue is synchronized with this Asana task by Unito

[johrstrom]

Hi, thanks for the ticket. Yea we can look into it.