[wp-trac] [WordPress Trac] #10458: lighttpd/1.4.22 does not populate _REQUEST['action'] for wp-login.php
WordPress Trac
wp-trac at lists.automattic.com
Tue Jul 21 23:00:50 UTC 2009
#10458: lighttpd/1.4.22 does not populate _REQUEST['action'] for wp-login.php
--------------------------+-------------------------------------------------
Reporter: myrond | Owner:
Type: defect (bug) | Status: new
Priority: normal | Milestone: Unassigned
Component: General | Version: 2.8
Severity: normal | Keywords:
--------------------------+-------------------------------------------------
Comment(by myrond):
I have tested the following wordpress releases:
2.8.0
2.3
I have tested the following lighttpd releases 1.4.19,1.4.20,1.4.22 all of
them exhibit the same behavior with both listed wordpress combinations.
2.3 will simply bounce you back to the login base, with 2.8 it has a
default switch which will ask you for a login (even though the cookie was
not deleted)
Both _REQUEST and _GET are not populated and they are empty; and the
workaround I've posted has been applied to numerous web applications which
have problems and need that data. (drupal, magento, others).
However upon further research it appears this problem only occurs on sites
which are using lighttpd rewrite rules.
namely:
{{{
url.rewrite-once = (
"^/(.*\.php)" => "$0", #(this line grabs the wp-login.php so it won't be
grabbed by
"^/(.*)$" => "/index.php/$1" #this line
)
}}}
This is a common rewrite used on lighttpd boxes, and the rewrite appears
to strip _REQUEST. Much apologies please disregard this or apply it
(makes no difference).
I suspect that anyone else who is using rewrite rules will apply a fix
similar to the one I have listed. all of the wp-admin stuff are excluded
by a previous (non listed rule) and as such do not have problems with the
_REQUEST variable.
--
Ticket URL: <http://core.trac.wordpress.org/ticket/10458#comment:3>
WordPress Trac <http://core.trac.wordpress.org/>
WordPress blogging software
More information about the wp-trac
mailing list