[Backport] fix: Strict-Transport-Security via proxy #11896
Conversation
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
2403905
approved these changes
Jan 7, 2026
kobergj
approved these changes
Jan 7, 2026
mklos-kw
force-pushed
the
backport/strict-transport-security-proxy
branch
2 times, most recently
from
ba3835c to
ac7a3f7
Compare
Member
Author
|
CI blocked by Codacy check, however Codacy shows no details on why it fails. Other PRs are fine, original PR was fine, will revisit in a moment. |
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
References: #11880 (fix: [OCISDEV-54] Strict-Transport-Security via proxy)
Description
Related Issue
Motivation and Context
How Has This Been Tested?
Screenshots (if appropriate):
Types of changes
Checklist: