Preprocess HTML: wrap Content-Security-Policy
meta tag into comment
#8075
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.
What it does
Wraps into comment (disables)
Content-Security-Policy
meta tag in HEAD section in webview HTML.It needs for Jira and Bitbucket extension, which use webviews to display some pages.
The extension opens a webview with initial HTML:
Java script
src
refers on the resource usingvscode-resource:
scheme in the URI. To have such resource being loaded, Theia pre-processes the URI before inserting the HTML.But if the webview has restrictions (
script-src vscode-resource:
) provided byContent-Security-Policy
meta tag, the browser blocks all the requests to that resources.The idea is to temporary wrapping into comment such meta tags while we don't have any solution how to handle resources with
vscode-resource:
andtheia-resource:
schemes.Original issue describing the problem eclipse-che/che#17081
How to test
In any webview
vscode-resource:
ortheia-resource:
scheme in the URIReview checklist