Make sure we properly ass well-known paths to index.php

[juliusknorr]

This makes sure we pass .well-known paths to index.php if they are not acme-challenge|pki-validation. The fallback for random files starting with "." is still preserved. Otherwise the rewrite to a 404 status page will cause issues with the get parameters not being preserved when the 404 is handled by our own ErrorDocument handling in

server/lib/private/Setup.php

Line 523 in d89a75b

$content .= "\nErrorDocument 404 " . $webRoot . '/';

Ref #24702

[ChristophWurst]

@daita please test with your setups :)

[ArtificialOwl]

green test on:

• local
• frontal with default setup
• frontal with htaccess.RewriteBase

👍

[faily-bot]

🤖 beep boop beep 🤖

Here are the logs for the failed build:

Status of 790: failure

jsunit

Show full log

[ArtificialOwl]

Not really important as there is a work around, but ...

Did some more test with nextcloud in a sub folder/path: https://example.net:8081/nextcloud/

With default setup, I just need (in apache config) to redirect the request from /.well-known/webfinger to /nextcloud/index.php/.well-known/webfinger. However, request/redirection on /nextcloud/.well-known/webfinger/ returns raw 404.

Now, with htaccess.RewriteBase set to '/nextcloud/ redirection still needs to be done using /nextcloud/index.php/.well-known/webfinger as request/redirection on /nextcloud/.well-known/webfinger/ have their $_GET empty ...