Skip to content

Conversation

teh-maxh
Copy link

The warning for a max-age > 10 years does not currently explain why that may be an issue. Explanatory text added.

header.go Outdated
"header.preloadable.max_age.over_10_years",
"Max-age > 10 years",
"FYI: The max-age (%d seconds) is longer than 10 years, which is an unusually long value.",
"FYI: The max-age (%d seconds) is longer than 10 years, which is an unusually long value, and may be disregarded by some browsers.",
Copy link
Collaborator

Choose a reason for hiding this comment

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

The wording "may be disregarded" makes it sound like the browser will disregard the max-age value (and thus the HSTS header) altogether, which is not the case. How about "may be capped at a lower value" instead?

Copy link
Author

Choose a reason for hiding this comment

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

That's a valid concern. Revising.

@lgarron
Copy link
Collaborator

lgarron commented Nov 28, 2020

For what it's worth, I believe:

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.

3 participants