permissionPolicy tweak, add Strict-Transport-Security header #105
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.
Tweaks:
permissionPolicy
header key - set to 'none' (next-safe default) instead of false, which omits the key/header altogetherPermissions-Policy
andFeature-Policy
headers. Gives myriad of warnings in console though, depending on browser (use false in dev to get rid of these):Strict-Transport-Security
(https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security) in the mix with some defaults.With these changes, great success: