[wp-trac] [WordPress Trac] #47814: 404's redirect to the front page

[WordPress Trac]

#47814: 404's redirect to the front page
--------------------------+------------------------------
 Reporter:  hal@…         |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Awaiting Review
Component:  Permalinks    |     Version:  5.2.2
 Severity:  normal        |  Resolution:
 Keywords:                |     Focuses:
--------------------------+------------------------------
Changes (by SergeyBiryukov):

 * component:  General => Permalinks


Old description:

> When there is a permalink "custom structure", 404's not within this
> structure redirect to the home page. Within the structure they work fine.
> Tested with twentynineteen theme, all plugins deactivated, and bare bones
> nginx config downloaded from nginx.org. The same scenario seems to work
> fine with Apache.
>
> Examples:
>
> $ curl -I -L https://www.kentuckybred.org/xyz
> HTTP/1.1 301 Moved Permanently
> Server: nginx
> Date: Wed, 31 Jul 2019 20:26:50 GMT
> Content-Type: text/html; charset=UTF-8
> Connection: keep-alive
> Vary: Accept-Encoding, Cookie
> X-Pingback: https://www.kentuckybred.org/xmlrpc.php
> X-Redirect-By: WordPress
> Location: https://www.kentuckybred.org/
> X-Frame-Options: SAMEORIGIN
> X-XSS-Protection: 1; mode=block
> X-Content-Type-Options: nosniff
> X-Permitted-Cross-Domain-Policies: master-only
> Strict-Transport-Security: max-age=31536000;includeSubdomains
>

> $ curl -I -L https://www.kentuckybred.org/resources/news/xyz
> HTTP/1.1 404 Not Found
> Server: nginx
> Date: Wed, 31 Jul 2019 20:27:02 GMT
> Content-Type: text/html; charset=UTF-8
> Connection: keep-alive
> Vary: Accept-Encoding
> Vary: Accept-Encoding, Cookie
> Expires: Wed, 11 Jan 1984 05:00:00 GMT
> Cache-Control: no-cache, must-revalidate, max-age=0
> Link: <https://www.kentuckybred.org/wp-json/>; rel="https://api.w.org/"
>
> Footnote: This site is not public yet, but scheduled for tomorrow launch.

New description:

 When there is a permalink "custom structure", 404's not within this
 structure redirect to the home page. Within the structure they work fine.
 Tested with twentynineteen theme, all plugins deactivated, and bare bones
 nginx config downloaded from nginx.org. The same scenario seems to work
 fine with Apache.

 Examples:
 {{{
 $ curl -I -L https://www.kentuckybred.org/xyz
 HTTP/1.1 301 Moved Permanently
 Server: nginx
 Date: Wed, 31 Jul 2019 20:26:50 GMT
 Content-Type: text/html; charset=UTF-8
 Connection: keep-alive
 Vary: Accept-Encoding, Cookie
 X-Pingback: https://www.kentuckybred.org/xmlrpc.php
 X-Redirect-By: WordPress
 Location: https://www.kentuckybred.org/
 X-Frame-Options: SAMEORIGIN
 X-XSS-Protection: 1; mode=block
 X-Content-Type-Options: nosniff
 X-Permitted-Cross-Domain-Policies: master-only
 Strict-Transport-Security: max-age=31536000;includeSubdomains


 $ curl -I -L https://www.kentuckybred.org/resources/news/xyz
 HTTP/1.1 404 Not Found
 Server: nginx
 Date: Wed, 31 Jul 2019 20:27:02 GMT
 Content-Type: text/html; charset=UTF-8
 Connection: keep-alive
 Vary: Accept-Encoding
 Vary: Accept-Encoding, Cookie
 Expires: Wed, 11 Jan 1984 05:00:00 GMT
 Cache-Control: no-cache, must-revalidate, max-age=0
 Link: <https://www.kentuckybred.org/wp-json/>; rel="https://api.w.org/"
 }}}
 Footnote: This site is not public yet, but scheduled for tomorrow launch.

--

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