An existing .well-known directory (as for Let's Encrypt) can prevent ActivityPub module's webfinger from working

Want to note that this is different from #2408321: Support RFC 5785 by whitelisting the .well-known directory →

Doing the opposite of ✨ Use a controller instead of writing to the .well-known directory Fixed might work LOL.

Or handling Let's Encrypt (and anything else through Drupal) https://www.drupal.org/project/letsencryptke →

A more reasonable workaround would seem to be something like:

https://geekblog.malcolmgin.com/2022/11/07/debugging-and-fixing-the-conf...

Still trying to find out if something is weird about our Apache configuration that is making it so .well-known does not play well.

OK! We (@wolcen) found that an easy change to the .htaccess in .well-known can make both let's encrypt and the ActivityPub module work.

Our hosting provider already had an .htaccess file in the .well-known folder (to ensure no other rules were preventing access for LetsEncrypt).

We added the last three lines to punt back to Drupal in the case that e.g. a LetsEncrypt validation file did not exist:

RewriteEngine On
satisfy any
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^ ../index.php [L]

This belongs in the webfinger module.

FWIW I have an existing .well-known directory, so it makes sense that is must have been a configuration thing. Should go onto the webfinger project page I guess too.

Moving to the right project