Allow access to .well-known prefix (RFC-5785) in default rewrite rules

[jakubboucek]

Automated configuration of rewrite in .htaccess ignore Well-Known Uniform Resource Identifiers (RFC-5785) defined in /.well-known/ prefix. This features can be designed outside of any WordPress application (for example: Letsencrypt project is runned from server shell and puts static files to ./.well-known/ webroot as verification process during requesting HTTPS certificate). Default configuration of configuration of rewrite in .htaccess can thwart this process because it redirect to index.php.

I know its contentious PR, but current state make confusions on some webhostings.

My tip: Just add after this line new rule:
RewriteCond %{REQUEST_URI} !^/.well-known/

[Presskopp]

Look what the drupal people do:
​https://www.drupal.org/node/2408321

[dd32]

I'm not sure I see the need for this.

The default WordPress rules allow for a file that exists to take precedence over WordPress handling the request. WordPress will respond with a non-200 response for a request to one of these URLs in the event the file doesn't exist.

There's also the possibility (I think there exists at least one) plugin for WordPress which specifically DOES want to handle /.well-known/ urls.

Perhaps a better question is, @jakubboucek What does the lack of this rule currently cause issue with?
It looks like Drupals rules are by default blocking access to /.* directories, so their handling of it isn't exactly relevant.

[desrosj]

Closing this out per @dd32's recommendation and a lack of reporter feedback.