Summary: | Prevent mod_rewrite from deadlooping | ||
---|---|---|---|
Product: | Apache httpd-1.3 | Reporter: | Dario Gomes <dariofg> |
Component: | mod_rewrite | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | CLOSED FIXED | ||
Severity: | enhancement | CC: | webmaster33 |
Priority: | P3 | ||
Version: | HEAD | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Dario Gomes
2003-02-27 04:50:00 UTC
he, you'll need a better system that finishs this endless loop under one minute ;-) It's a known issue. You're simply creating an endless loop of internal redirects. Thatswhy you already should test your rules before putting them on a production server. However, I'm changing this to an Enhancement request. We should be able to set a configurable limit of maximum redirects issued by mod_rewrite. Thanks for using Apache! The problem is I run a shared hosting server, and I have no control of the rules my users put on their sites... I got the server locked up two times before I found the source of the problem! Why doesn't this bug affect Apache 2.0.4x? Maybe they've worked out this issue already? -Dario In 2.0 the trick doesn't work with your ruleset, because of a different behaviour of mod_dir. You can crash the server, for example, with the following in a htaccess file (in docroot): RewriteEngine On RewriteBase / RewriteRule (.*) / [L] However, a configurable limit was introduced in 2.1 and is proposed for backport. FYI: The enhancement will appear in the next releases (1.3.28 and 2.0.45). |