Add cache-control headers to front_api#324
Merged
Merged
Conversation
Irozuku
reviewed
Oct 8, 2025
Irozuku
reviewed
Oct 8, 2025
Irozuku
approved these changes
Oct 9, 2025
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
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.
Summary
Improves how the frontend
index.htmlfile is served by adding cache-control headers.This ensures that users always receive the latest version of the React build after a new release, avoiding the need to manually refresh with Shift + F5.
Type of change
Changes
DashAI/back/api/front_api.pyto addCache-Control,Pragma, andExpiresheaders when servingindex.html.How to Test
yarn build.python -m DashAIor the built.exe).http://localhost:8000/app/).Notes
This change only affects the
index.htmlroute.Static assets (JS, CSS, images) remain cached normally since their filenames are hash-based.