[wp-trac] [WordPress Trac] #37201: Allow access to .well-known prefix (RFC-5785) in default rewrite rules

[WordPress Trac]

#37201: Allow access to .well-known prefix (RFC-5785) in default rewrite rules
-------------------------------+-----------------------------
 Reporter:  jakubboucek        |       Owner:  (none)
     Type:  feature request    |      Status:  closed
 Priority:  normal             |   Milestone:
Component:  Rewrite Rules      |     Version:
 Severity:  normal             |  Resolution:  wontfix
 Keywords:  reporter-feedback  |     Focuses:  administration
-------------------------------+-----------------------------
Changes (by desrosj):

 * keywords:  reporter-feedback close => reporter-feedback
 * status:  new => closed
 * version:  4.6 =>
 * resolution:   => wontfix


Old description:

> 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 [https://core.trac.wordpress.org/browser/trunk/src
> /wp-includes/class-wp-rewrite.php#L1517 this line] new rule:
> `RewriteCond %{REQUEST_URI} !^/.well-known/`

New description:

 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 [https://core.trac.wordpress.org/browser/trunk/src
 /wp-includes/class-wp-rewrite.php#L1517 this line] new rule:
 `RewriteCond %{REQUEST_URI} !^/.well-known/`

--

Comment:

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

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/37201#comment:3>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform