Don't wait for this bug. As long as no one has a good idea how to handle this,
there will be no patch.
Here the commit message for the revert:
Revert url decoding+simplifying before matching of mod_rewrite/mod_redirect
- Lot of regressions (we forgot to reencode the result)
- Generic problem: af
ok and if I read the last activity report on this bug, they will
not fix this bug tomorow :
Updated by stbuehler 101 days ago
* Status changed from Fixed to Reopened
* Target version changed from 1.4.20 to 1.4.21
* Patch available set to No
Patch(es) reverted in 1.4.x (r2362) - t
there is lighttpd 1.4.22 in our svn repo. Last thing which left before
release is to check lighttpd-1.4.x_rewrite_redirect_decode_url.patch.
Upstream bug for that is http://redmine.lighttpd.net/issues/1720 with
such info:
Patch(es) reverted in 1.4.x (r2362) - too many regressions came up.
See comm
Package: lighttpd
Version: 1.4.19-5
Severity: wishlist
Lighttp is now in 1.4.22 in the stable release lot of security fix ...
http://www.lighttpd.net/2008/9/30/1-4-20-Otherwise-the-terrorists-win
http://www.lighttpd.net/2009/2/16/1-4-21-yes-we-can-do-another-release
http://www.lighttpd.net/2009/3
4 matches
Mail list logo
