使用PHP处理站点范围的URL重写

Question

I'm looking into the feasibility of using PHP - instead of mod_rewrite - to handle URL canonicalization. I'm looking to be able to map a large number of different URLs to a given physical PHP page, and handle 301's and 404's in a more centralized and maintainable way. This will include common misspellings, aliases, search engine friendly URL parameters, and the like. These needs seem well outside the power of mod_rewrite , so I'm looking into other options.

I'm thinking I would create a canonical.php script which I map every page to with the following in .htaccess ( borrowed from this post ):

RewriteEngine On
RewriteBase /
RewriteRule ^(.*)$ canonical.php/$1?%{QUERY_STRING} [L]

And then canonical.php would do whatever URL parsing / db lookups / redirects / etc. are necessary, then simply include /the/appropriate/file.php for the given request.

Is this a reasonable course of action? Is such functionality actually feasible with mod_rewrite directly? (DB lookups and the like aside) will this be distinctly slower than mod_rewrite ? Is there any other methodology that's more robust than a PHP wrapper?

Answer 1

You're talking about routing, which plenty of frameworks do. Take a look at this answer: https://stackoverflow.com/questions/115629/simplest-php-routing-framework

Answer 2

What I would suggest and what I use is a php file that gets called everytime when a 404 is encountered and it stores the url encountered. Then once a week I go to the management console and I map the wrongly spelled mistyped, old urls, searchengine's history url's to the current existing urls then I hit the parse button and it spews out a new updated .htaccess file out for me.

That way you lighten the load on your database, loading time, compiling time and redirecting time.

Just my 2 cents.

Answer 3

还没有机会进行测试，但是这个答案使我想到了Apache的FallbackResource指令，这听起来很有希望。