Repository navigation
docs(hosting): align static asset CSP on 6.4 - #2614
Closed
Jonas Elfering (keulinho) wants to merge 1 commit into
Closed
Jonas Elfering (keulinho) wants to merge 1 commit into
Jonas Elfering (keulinho) wants to merge 1 commit into
Conversation
Developer Docs healthcheckStatus: Completed with |
3 of 5 tasks
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 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.
1. Why is this change necessary?
The published 6.4 server examples should use the same static HTML/SVG policy as the current hosting documentation.
2. What does this change do, exactly?
Backport the Apache and Nginx example changes from #2613. Existing HTML under
media/andthumbnail/, and static SVG files, receivescript-src 'none'; object-src 'none'; frame-src 'none'; base-uri 'none'; form-action 'none'. Application-rendered HTML and bundled HTML apps retain their response policies. Preserve the older installer/recovery routing.3. Describe each step to reproduce the issue or behaviour.
Use the updated example and request stored HTML/SVG, then rendered HTML and a bundled HTML app. Only the stored assets receive the dedicated policy.
Validation: the extracted 6.4 Nginx example passes native syntax validation and 13 real HTTP cases in an isolated Docker setup with fixture PHP responses. Markdown lint uses the current docs configuration. Existing obsolete
http2_push_preloadwarnings on older Nginx examples are outside this change.4. Please link to the relevant issues (if any).
5. Checklist