The max-age value used by the default HSTS header is no longer correct#121
Merged
GaProgMan merged 6 commits intoGaProgMan:mainfrom Nov 28, 2024
Merged
Conversation
GaProgMan
approved these changes
Nov 28, 2024
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rationale for this PR
Previous versions of the OWASP Recommended Secure Headers had recommended that the max-age value for Strict-Transport-Security headers should be 63072000 (730 days). However, the recommendation is to now use 31536000 (365 days).
Also included is a cleanup of unused using strings and a minor version bump.