Eric, thank you. Now I see it's mentioned at http://httpd.apache.org/docs/2.0/rewrite/rewrite_tech.html mentions that 'in per-directory context mod_rewrite first rewrites the filename... and then initiates a new internal sub-request with the new URL. This restarts processing of the API phases.' I originally only read http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html. It says 'Because the per-directory rewriting comes late in the process, the rewritten request has to be re-injected into the Apache kernel' - but it's not clear what is actually hapening to the request. Whoever maintains this web page, please could you append something like 'as if it were a new request - see [http://httpd.apache.org/docs/2.0/rewrite/rewrite_tech.html ]' or ' and it checks for any applicable rules again, from all its per-server or per-directory contexts' (or something more clear). Thank you 2008/11/26 Eric Covener <covener@xxxxxxxxx>: >> rewriter log says it rewrites to /index.php first (1st rule) and then >> it rewrites it to /set_cookie.php (2nd rule). I thought [L] and [NS] >> should stop any further rules. What am I missing? > > In per-directory context, any time you make a change the entire cycle > is restarted -- 'L' only applies to the current pass. --------------------------------------------------------------------- The official User-To-User support forum of the Apache HTTP Server Project. See <URL:http://httpd.apache.org/userslist.html> for more info. To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx " from the digest: users-digest-unsubscribe@xxxxxxxxxxxxxxxx For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|