fix(www): ensure state-changing GETs are never browser-cached - #612
Merged
Merged
Conversation
Two identical keystrokes make identical URLs. The browser can serve the second one from its cache, so it never reaches the server (e.g. typing "oo" prints only one "o"). Send no-cache headers on every API response and turn off caching for jQuery GETs in the frontend. Signed-off-by: Cedric Hombourger <cedric.hombourger@siemens.com>
fmoessbauer
reviewed
Sep 22, 2026
fmoessbauer
approved these changes
Sep 23, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Two identical keystrokes make identical URLs. The browser can serve the second one from its cache, so it never reaches the server (e.g. typing "oo" prints only one "o"). Send no-cache headers on every API response and turn off caching for jQuery GETs in the frontend.