You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In Debugging info is RewriteCond before RewriteRule, but the Apache first evaluates the first parameter (pattern) in the RewriteRule and only on match begins to test the conditions in the RewriteCond written before that RewriteRule.
The example lacks pattern testing between steps 1 (RewriteEngine On) and 2 (RewriteCond %{QUERY_STRING} ^qs$).
Manual says: The rewriting engine loops through the ruleset rule by rule (RewriteRule directives) and when a particular rule matches it optionally loops through existing corresponding conditions (RewriteCond directives). For historical reasons the conditions are given first, and so the control flow is a little bit long-winded. https://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset
The text was updated successfully, but these errors were encountered:
@kajman-cz thanks for creating this issue. Do you have a practical example where this behavior introduces bugs in the htaccess tester? That would help us understand the exact problem a bit better and to implement improvements to the tool.
In Debugging info is RewriteCond before RewriteRule, but the Apache first evaluates the first parameter (pattern) in the RewriteRule and only on match begins to test the conditions in the RewriteCond written before that RewriteRule.
The example lacks pattern testing between steps 1 (RewriteEngine On) and 2 (RewriteCond %{QUERY_STRING} ^qs$).
Manual says:
The rewriting engine loops through the ruleset rule by rule (RewriteRule directives) and when a particular rule matches it optionally loops through existing corresponding conditions (RewriteCond directives). For historical reasons the conditions are given first, and so the control flow is a little bit long-winded.
https://httpd.apache.org/docs/current/rewrite/tech.html#InternalRuleset
The text was updated successfully, but these errors were encountered: