-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use dclone on cache_control #1
Comments
I'm having trouble seeing this happening. Does this happen for requests to the same file? Different files? Files of the same type? When there's a global default? When there's an extension specific default? I've ran a ton of tests and can't seem to recreate this bug. I need more info, or some kind of an example. |
It's right there in the code:
I really don't know how to explain it any further without insulting your intelligence. |
I saw the problem in the code, realized it's wrong, but for some reason the tests did not display that behavior, though I might be missing something. Anyway, bug fixed in new version (will release later today), thanks for reporting. |
_determine_cache_control
is grabbing thecache_control
variable and then stuffing amax-age
item in there. Sincecache_control
is an arrayref, the original default is tainted with an ever-growing set of duplicatemax-age
items.The
cache_control
default needs to be cloned prior to modification.The text was updated successfully, but these errors were encountered: