Skip to content
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

core(byte-efficiency): combine multiple cache-control headers if found #5745

Merged
merged 1 commit into from
Aug 14, 2018

Conversation

justinribeiro
Copy link
Contributor

Per rfc2616, "Multiple message-header fields with the same field-name MAY be present in a message if and only if the entire field-value for that header field is defined as a comma-separated list [i.e., #(values)]". cache-control is defined as comma separated list, and as reported in #5742 this case is not handled correctly resulting in misreported files.

This PR fixes that denoted case within uses-long-cache-ttl.js and adds a test to verify this going forward.

image

Resolves #5742

@justinribeiro justinribeiro changed the title fix(core/byte-efficiency): combine multiple cache-control headers if found core(byte-efficiency): combine multiple cache-control headers if found Jul 28, 2018
Copy link
Collaborator

@patrickhulce patrickhulce left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nice fix thanks @justinribeiro! 🎉

@patrickhulce patrickhulce merged commit bb44a7d into GoogleChrome:master Aug 14, 2018
@justinribeiro justinribeiro deleted the issue-5742 branch September 8, 2018 00:49
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cache Control Header not parsed correctly when multiple headers with same field name returned
2 participants