You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: custom/conf/app.example.ini
+13-1Lines changed: 13 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -2540,7 +2540,19 @@ LEVEL = Info
2540
2540
;; * sanitized: Sanitize the content and render it inside current page, default to only allow a few HTML tags and attributes. Customized sanitizer rules can be defined in [markup.sanitizer.*] .
2541
2541
;; * no-sanitizer: Disable the sanitizer and render the content inside current page. It's **insecure** and may lead to XSS attack if the content contains malicious code.
2542
2542
;; * iframe: Render the content in a separate standalone page and embed it into current page by iframe. The iframe is in sandbox mode with same-origin disabled, and the JS code are safely isolated from parent page.
2543
-
;RENDER_CONTENT_MODE=sanitized
2543
+
;RENDER_CONTENT_MODE = sanitized
2544
+
;; The sandbox applied to the iframe and Content-Security-Policy header when RENDER_CONTENT_MODE is `iframe`.
2545
+
;; It defaults to a safe set of "allow-*" restrictions (space separated).
2546
+
;; You can also set it by your requirements or use "disabled" to disable the sandbox completely.
2547
+
;; When set it, make sure there is no security risk:
2548
+
;; * PDF-only content: generally safe to use "disabled", and it needs to be "disabled" because PDF only renders with no sandbox.
2549
+
;; * HTML content with JS: if the "RENDER_COMMAND" can guarantee there is no XSS, then it is safe, otherwise, you need to fine tune the "allow-*" restrictions.
2550
+
;RENDER_CONTENT_SANDBOX =
2551
+
;; Whether post-process the rendered HTML content, including:
0 commit comments