Missing IDN conversion in Content-Security-Policy builder

[Sprinterfreak]

Describe the bug
richdocuments breaks entire nextcloud instance if installed on an instance with unicode domain.
Adds raw unicode domain to the Content-Security-Policy-Header which makes browsers ignore those and therefore prevent any assets from being loaded. Nextcloud without javascript, images and css doesn't look that good.

To Reproduce
Install richdocuments on an instance with idn domain.

Expected behavior
FQDN in the Content-Security-Policy-Header must be idn_ascii converted

See nextcloud/server#39555 for details (including patch)

@kesselb has allready developed a patch for that nextcloud/server#39555 (comment), which I can confirm working.

[Sprinterfreak]

Still affects richdocuments 8.1.1

[Sprinterfreak]

Still affects richdocuments 8.2.3 although the responsible code has been rewritten

[juliushaertl]

Pasting this here for reference:

https://www.php.net/manual/de/function.idn-to-ascii.php

Index: lib/Listener/CSPListener.php
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/lib/Listener/CSPListener.php b/lib/Listener/CSPListener.php
--- a/lib/Listener/CSPListener.php	(revision 1b609dac1bf216c4913188ab3861f37fabb49147)
+++ b/lib/Listener/CSPListener.php	(date 1690223340061)
@@ -66,6 +66,7 @@
 		);
 
 		$urls = array_filter($urls);
+		$urls = array_map(fn($url) => idn_to_ascii($url), $urls);
 
 		$policy = new EmptyContentSecurityPolicy();
 		$policy->addAllowedFrameDomain("'self'");

[juliushaertl]

Added a commit to #3315