[mod] enable CSS & JS cache busting by default #4433
Closed
Conversation
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
The static files (CSS & JS) are cached in the browser for one year. If we have changes to the CSS or JS files, these are not yet transported to the client by default, which causes problems and irritations on the client side. Related: - searxng#4415 (comment) - searxng#932 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Contributor
|
As far I remember, and I can't remember why, this can't be enabled outside the docker image. |
Member
Author
Its a long time ago .. can't remember last state of this topic, but may you refer to this: |
return42
added a commit
to return42/searxng
that referenced
this pull request
Mar 6, 2025
As long we don't have a working solution for cache busting [3][4] we should not set an expire time in thw uWSGI config. The default procedure in every web browser is the "304 Not Modified" [2] and this default procedure should also be sufficient for us as long as we have not implemented a complete alternative (cache busting) / form [1] > By default uWSGI will add a Last-Modified [2] header to all static responses, > and will honor the If-Modified-Since [2] request header. [1] https://uwsgi-docs.readthedocs.io/en/latest/StaticFiles.html#setting-the-expires-headers [2] https://developer.mozilla.org/de/docs/Web/HTTP/Status/304 [3] searxng#4433 [4] searxng#964 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Member
Author
|
For a interim solution I send PR: |
return42
added a commit
that referenced
this pull request
Mar 8, 2025
As long we don't have a working solution for cache busting [3][4] we should not set an expire time in thw uWSGI config. The default procedure in every web browser is the "304 Not Modified" [2] and this default procedure should also be sufficient for us as long as we have not implemented a complete alternative (cache busting) / form [1] > By default uWSGI will add a Last-Modified [2] header to all static responses, > and will honor the If-Modified-Since [2] request header. [1] https://uwsgi-docs.readthedocs.io/en/latest/StaticFiles.html#setting-the-expires-headers [2] https://developer.mozilla.org/de/docs/Web/HTTP/Status/304 [3] #4433 [4] #964 Signed-off-by: Markus Heiser <markus.heiser@darmarit.de>
Member
Author
|
Obsolete since: |
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.
The static files (CSS & JS) are cached in the browser for one year. If we have changes to the CSS or JS files, these are not yet transported to the client by default, which causes problems and irritations on the client side:
label:"clear browser cache"Related: