[wp-trac] [WordPress Trac] #20746: Accessing non-existing theme folder in Network install gives 500 error

[WordPress Trac]

#20746: Accessing non-existing theme folder in Network install gives 500 error
---------------------------------------+-----------------------------
 Reporter:  arkimedia                  |       Owner:
     Type:  defect (bug)               |      Status:  reopened
 Priority:  normal                     |   Milestone:  Future Release
Component:  Rewrite Rules              |     Version:  3.3.2
 Severity:  normal                     |  Resolution:
 Keywords:  needs-testing needs-patch  |     Focuses:  multisite
---------------------------------------+-----------------------------
Changes (by jeremyfelt):

 * keywords:  has-patch needs-testing => needs-testing needs-patch
 * milestone:  Awaiting Review => Future Release


Comment:

 Hey everyone, thanks for hanging in there. I've been able to confirm and
 test the following.

 In 4.2:

 * `http://foo.bar/subsite/non-dir/` responds as a WordPress 404.
 * `http://foo.bar/subsite/wp-content/non-dir/` responds as an Apache 500.
 * `http://foo.bar/subsite/wp-content/non-file.txt` responds as an Apache
 404.
 * `http://foo.bar/subsite/wp-content/non-dir/non-file.txt` responds as an
 Apache 500.

 After modifying the wp-* line in htaccess to the suggested `RewriteRule
 ^[_0-9a-zA-Z-]+/(wp-(content|admin|includes).*) $1 [L]`

 * `http://foo.bar/subsite/non-dir/` responds as a WordPress 404.
 * `http://foo.bar/subsite/wp-content/non-dir/` responds as a WordPress
 404.
 * `http://foo.bar/subsite/wp-content/non-file.txt` responds as an
 WordPress 404.
 * `http://foo.bar/subsite/wp-content/non-dir/non-file.txt` responds as a
 WordPress 404.

 How I would expect things to respond:

 * `http://foo.bar/subsite/non-dir/` responds as a WordPress 404.
 * `http://foo.bar/subsite/wp-content/non-dir/` responds as Apache 403
 forbidden.
 * `http://foo.bar/subsite/wp-content/non-file.txt` responds as Apache 404
 not found.
 * `http://foo.bar/subsite/wp-content/non-dir/non-file.txt` responds as
 Apache 404 not found.

 Overall - I think it would be appropriate to avoid loading the entire
 WordPress 404 process for missing static files. My Apache rewrite memories
 have mostly been lost to Nginx rules. Any ideas on how that could be
 handled?

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