You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jan 22, 2024. It is now read-only.
Jaggr doesn't include Cache-Control:max-age= using the expires server-side config property in responses that don't include a cb= or cacheBust = query arg. This is to prevent unwanted far-future caching of resources. Now that jaggr can be configured as a regular resource servlet, this is too inflexible as applications may not always have control over what query arg is used to specify the cachebust argument (e.g. ckeditor uses t=XXX). A mechanism is needed to specify custom URL patterns that will include the Cache-Control:max-age= header even if the request URL doesn't include the cb= or cacheBust= query args.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Jaggr doesn't include Cache-Control:max-age= using the
expires
server-side config property in responses that don't include a cb= or cacheBust = query arg. This is to prevent unwanted far-future caching of resources. Now that jaggr can be configured as a regular resource servlet, this is too inflexible as applications may not always have control over what query arg is used to specify the cachebust argument (e.g. ckeditor uses t=XXX). A mechanism is needed to specify custom URL patterns that will include the Cache-Control:max-age= header even if the request URL doesn't include the cb= or cacheBust= query args.The text was updated successfully, but these errors were encountered: