Rewrite Problem – L(ast) not being respected?

by

The L flag says “do not execute any more rules in the ruleset,” which oddly enough does not imply that no more rules will be executed by mod_rewrite.

When you specify mod_rewrite directives in a per-directory context, like with .htaccess or the Directory section of a server or virtual server configuration, the rewrite comes late in the Apache processing stage. To do its magic here, mod_rewrite has to perform an internal redirect every time that your URL is rewritten.

Since your rewrite could point you to a different directory, mod_rewrite assigns itself as the handler for this redirection so that it can go through whatever rules it may find at the new location you’ve sent the request to. Often, since you’re only dealing with a single .htaccess file in your root, the rules in the “new” location happen to be the ones that caused the rewrite in the first place.

So, in your case, the following happens:

  • Request made for /css/A01EF
  • mod_rewrite starts the ruleset
  • ^css/([0-9a-fA-F]{32})$ -> assets.php?hash=A01EF
  • L flag stops rewrite and forces internal redirect to assets.php?hash=A01EF
  • mod_rewrite starts the ruleset over again
  • ^([a-zA-Z0-9_.-]+)$ -> index.php?url=assets.php&hash=A01EF (you could use QSA here, by the way)
  • L flag stops rewrite and forces internal redirect to index.php?url=assets.php&hash=A01EF

It’s likely that this loop would continue, but mod_rewrite recognizes that you’re redirecting to the same page and ignores your rewrite after this point.

This whole process happens to be why the two conditions…

RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

…are so common in .htaccess mod_rewrite rulesets, given that they provide an easy way to determine if the URL has already been rewritten to the intended real resource. You could use them, or you can exclude the index.php rewrite when the request has been rewritten to assets.php:

RewriteCond %{REQUEST_URI} !^/assets.php
RewriteRule ^([a-zA-Z0-9_.-]+)$ index.php?url=$1&%{QUERY_STRING} [L]

More Related Contents:

  1. Reference: mod_rewrite, URL rewriting and “pretty links” explained
  2. Remove .php extension with .htaccess
  3. Tips for debugging .htaccess rewrite rules
  4. htaccess redirect to https://www
  5. htaccess remove index.php from url
  6. Hidden features of mod_rewrite
  7. What does RewriteBase do and how to use it?
  8. How to debug .htaccess RewriteRule not working
  9. Forbidden You don’t have permission to access / on this server [closed]
  10. .htaccess rewrite query string as path
  11. How to redirect URLs based on query string?
  12. mod_rewrite: remove trailing slash (only one!)
  13. .htaccess rewrite “/book.php?id=1234” to “/book/1234”
  14. mod_rewrite with anchor link
  15. CSS, JS and images do not display with pretty url
  16. mod_rewrite: remove query string from URL?
  17. Redirect requests only if the file is not found?
  18. Multiple RewriteRules for single RewriteCond in .htaccess
  19. Difference between $1 vs %1 in .htaccess
  20. How can I mod_rewrite and keep query strings?
  21. Internal URL rewrite no longer working after upgrading Apache to 2.4
  22. RewriteCond to match query string parameters in any order
  23. htaccess RewriteRule page with query string
  24. URL rewriting for different protocols in .htaccess
  25. The Redirection of Multiple Parked Domains doesn’t Work with Filename [closed]
  26. AH10411 error: Managing spaces and %20 in apache mod_rewrite
  27. Htaccess: add/remove trailing slash from URL
  28. Rewriting an arbitrary number of path segments to query parameters
  29. Remove .php from urls with htaccess
  30. How to redirect non-www to www URL’s using htaccess?

Leave a Comment