Add ReferrerPolicy to Secure middleware #1363
Merged
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.
This Pull Request adds
Referrer-Policy
to the Secure middleware.The goal of this header is to hide potentially sensitive referrer information (such as the origin or path of the original request).
Example:
If a user visits the hypothetical
https://echo.labstack.com/?some_secure_token=foobarbaz
, a request is made tohttps://use.fontawesome.com/releases/v5.0.8/js/all.js
. This request contains a headerReferer: https://echo.labstack.com/?some_secure_token=foobarbaz
. FontAwesome does not need to knowsome_secure_token
to give us icons, so we should limit the information they get from us in the Referer header. This can be done by setting aReferrer-Policy
header.