Uh oh!
There was an error while loading. Please reload this page.
Allow "same-origin" as "Referrer-Policy" (Backport to stable14) - #11950
Merged
MorrisJobke merged 1 commit intoOct 22, 2018
Merged
Allow "same-origin" as "Referrer-Policy" (Backport to stable14)#11950MorrisJobke merged 1 commit into
MorrisJobke merged 1 commit into
Conversation
Fixes#11531 Although "same-origin" is more strict than e.g. strict-origin it showed up a warning in setupcheck Based on https://scotthelme.co.uk/a-new-security-header-referrer-policy/ Signed-off-by: Moritz Beck <git@birkenstab.de>
rullzer
requested review from
ChristophWurst, MorrisJobke, juliusknorr, nickvergessen and rullzerOctober 21, 2018 11:31
rullzer
approved these changes
Oct 21, 2018
MorrisJobke
approved these changes
Oct 22, 2018
Merged
Merged
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 freeto join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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.
Fixes#11531
Although "same-origin" is more strict than e.g. strict-origin it showed up a warning in setupcheck
Based on https://scotthelme.co.uk/a-new-security-header-referrer-policy/
Signed-off-by: Moritz Beck git@birkenstab.de