View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0023324||mantisbt||performance||public||2017-09-06 13:06||2018-03-30 05:32|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Target Version||2.7.0||Fixed in Version||2.7.0|
|Summary||0023324: Generated css, js code should be cached by browser|
Generated files like:
Are currently not cached by clients, increasing load time and server request processing.
Usually, the content of those files is not changed unless there is a change in global configuration, so it's safe to be cached.
|Tags||No tags attached.|
in the same browser?
let's see if that can be accounted with some sort of headers
Not sure we are talking about the same thing.
E.g status_config.php generates CSS code (colors) based on config_get( 'status_enum_string');
This could be dependant on user, but not on project.
dependant on user, but current content i think it's not based on project:
Dependant on language (not on user directly), but not on poject.
yes, i understand.
MantisBT: master 712edd2d
Committer: vboctor Details Diff
|Allow caching of generated js/css files
Allow client caching of dynamically generated css and js files.
Default headers disable explicitly caching of application pages, but
these generated files don't change usually between page loads.
By disabling default headers, the cacheability is defined by the server
The included resources are referenced by a URL query built with a
parameter that differentiates content that may have changed based on
current user, project, language, etc. This parameter would force a
reload in case the content may be different from the cached version.
|mod - core/helper_api.php||Diff File|
|mod - core/html_api.php||Diff File|
|mod - css/status_config.php||Diff File|