DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT <http://issues.apache.org/bugzilla/show_bug.cgi?id=40046>. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=40046 ------- Additional Comments From [EMAIL PROTECTED] 2006-07-17 08:11 ------- This is not determined from any rewrite rule that i can post but from this code snippet from the latest release of apache 2.2.2. httpd-2.2.2/modules/mappers/mod_rewrite.c , line 3939 and following if (p->flags & RULEFLAG_PASSTHROUGH) { rewritelog((r, 2, perdir, "forcing '%s' to get passed through " "to next API URI-to-filename handler", r->filename)); r->filename = apr_pstrcat(r->pool, "passthrough:", r->filename, NULL); changed = ACTION_NORMAL; break; } The break statement causes the loop over rewrite rules to be exited from. A rewrite rule that exhibits this behaviour is for example: RewriteCond %{QUERY_STRING} !moose=1 RewriteRule /(.*) /$1?moose=0 [PT,QSA] RewriteRule /(.*) /$1 [E=TEST:1] Which doesn't result in TEST being set if moose=1 is not present in the query string. This is non-documented non-obvious behaviour. (Yes there are many other ways of rewriting the rules to avoid this, if you consider this behaviour to be correct / to spec, please document it). -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
