Repository navigation
fix: include the 'Strict-Transport-Security' header to enforce HTTPS-only communication - #2244
Merged
Merged
Conversation
…munications will be sent over HTTPS'
github-actions
Bot
added
package: wallet/frontend
Tymmmy
approved these changes
Sep 21, 2026
dragosp1011
approved these changes
Sep 21, 2026
|
🎉 This PR is included in version 0.10.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
3 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.
Context
Changes
Ensure all communications are sent over HTTPS by including the 'Strict-Transport-Security' response header and preventing HTTPS click-through prompts in browsers.
The 'max-age' flag is set to 12 months and the 'includeSubDomains' flag is included