[TASK] Add nonce metatag to TYPO3 backend as well #88
Conversation
This file contains 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
This adds the special nonce metatag to the TYPO3 backend that vite uses to inject its assets CSP-friendly when the dev server is used. Naturally, this is a security-relevant change since it fiddles with the security policies in the TYPO3 backend. However, since this is really only used if the dev server is activated in the extension configuration, this is not critical for production systems. On the flipside it enables the usage of the Vite dev server for some backend use cases, for example in backend module templates or in preview templates for content elements. Resolves: #82
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.
This adds the special nonce metatag to the TYPO3 backend that vite uses to inject its assets CSP-friendly when the dev server is used. Naturally, this is a security-relevant change since it fiddles with the security policies in the TYPO3 backend. However, since this is really only used if the dev server is activated in the extension configuration, this is not critical for production systems.
On the flipside it enables the usage of the Vite dev server for some backend use cases, for example in backend module templates or in preview templates for content elements.
Resolves: #82