$conf, $runtime; function_exists('chdir') AND chdir(APP_PATH); $r = 'mysql' == $conf['cache']['type'] ? website_set('runtime', $runtime) : cache_set('runtime', $runtime); } function runtime_truncate() { global $conf; 'mysql' == $conf['cache']['type'] ? website_set('runtime', '') : cache_delete('runtime'); } register_shutdown_function('runtime_save'); ?>404 error - Why does my WordPress show a 404 message for 403 forbidden directories?|Programmer puzzle solving

Programmer puzzle solving

    最新消息：Welcome to the puzzle paradise for programmers! Here, a well-designed puzzle awaits you. From code logic puzzles to algorithmic challenges, each level is closely centered on the programmer's expertise and skills. Whether you're a novice programmer or an experienced tech guru, you'll find your own challenges on this site. In the process of solving puzzles, you can not only exercise your thinking skills, but also deepen your understanding and application of programming knowledge. Come to start this puzzle journey full of wisdom and challenges, with many programmers to compete with each other and show your programming wisdom! Translated with DeepL.com (free version)
    你的位置： HOME>matter>404 error - Why does my WordPress show a 404 message for 403 forbidden directories?

    404 error - Why does my WordPress show a 404 message for 403 forbidden directories?

    matteradmin8PV0评论

    I'm not sure if this is specific to my site or not, but if anyone knows how to override this behavior, that would be most appreciated! I have WordPress installed in the root directory of my server. There is also an unrelated sub-directory we'll call 'restricted-dir'. I have added an .htaccess file inside that directory with the following code:

    Deny from all

    Without that command, if a user visits www.my-domain/restricted-dir/ it would list all contents. I would like the user to receive the server's typical 403 Forbidden message, but instead WordPress kicks in and directs the user to my 404 page on my website.

    Is there anything I can do to make the 403 page show up instead of the 404 page along with my entire WordPress install?

    I'm not sure if this is specific to my site or not, but if anyone knows how to override this behavior, that would be most appreciated! I have WordPress installed in the root directory of my server. There is also an unrelated sub-directory we'll call 'restricted-dir'. I have added an .htaccess file inside that directory with the following code:

    Deny from all

    Without that command, if a user visits www.my-domain/restricted-dir/ it would list all contents. I would like the user to receive the server's typical 403 Forbidden message, but instead WordPress kicks in and directs the user to my 404 page on my website.

    Is there anything I can do to make the 403 page show up instead of the 404 page along with my entire WordPress install?

    • 404-error
    Share Improve this question asked Oct 30, 2017 at 18:34 EricaErica 1715 bronze badges 3
    • Are you using apache 2.2 or 2.4? For 2.2, your try should work imho, for 2.4, you should use Require all denied, see also the upgrade guide. – janh Commented Oct 30, 2017 at 18:39
    • It's only 2.2 so I would have thought so too, unless something else is overriding it. I had hoped it was a WP thing that could be overwritten. – Erica Commented Oct 30, 2017 at 18:48
    • Changing my WordPress theme did not change the results. I wanted to check since it had custom 404 settings. – Erica Commented Oct 30, 2017 at 18:49
    Add a comment  | 

    2 Answers 2

    Reset to default 0

    Thinking on it for a minute, I suppose it has something to do with the rewrite rules from the WP .htacces is kicking in and rewriting the request to WP. It doesn't totally make sense to me, because WP's rewrite rules actually ignore directories, and I cannot reproduce it with a quick test, but there might be other factors at play in your environment.

    Adding 

    RewriteEngine On
RewriteRule ^restricted-dir - [F,L]

    in the WP .htaccess before the WordPress Rewrite Rules should have the same result, denying access to restricted-dir with a 403 response.

    This question is old but in case anyone else comes across with the same problem, I found the answer in this ticket:

    https://wordpress.stackexchange/a/20274/31889

    (For me solution #3 was the ticket, but I also have the first two in place so maybe it was a combination.)

    Articles related to this article

    Post a comment

    comment list (0)

    1. No comments so far