The `Cache-Control: max-age=...` response header is important, because it influences when a browser will check for changes of a page/file again. Currently, the Eclipse Foundation webserver uses inconsistent `max-age` values for different types of content: * `*.html` (including directories, implicitly `index.html`): `max-age=600` (10 minutes) * `*.css`: `max-age=3600` (1 hour) * `*.js`: `max-age=3600` (1 hour) * `*.png`: `max-age=3600` (1 hour) * `*.pdf`: no `max-age` * `.versions`: no `max-age` This has several implications: * Users may not see new HTML pages up to 10 minutes after we release a new version. * Users may not see new CSS/JS/PNG files up to an hour after we release a new version. * Users may potentially never (or not for a long time) see new versions in the version selector, after we release a new version. We should probably update our release process to account for this. We should also ask the Eclipse Foundation to change it to 10 minutes for all files.