This article I found on the Mind Tree Blog sort of covers old ground for me, but it was interesting nonetheless. It’s interesting the way he doesn’t forward specific things, but rather everything in the URL… so we’d forward something like:
http://www.asgrim.com/channel/Google/news/something/
to:
http://www.asgrim.com/index.php?p=channel/Google/news/something/
and letting the PHP script decode the specifics of the URL, rather than setting up specific forwards like:
http://www.asgrim.com/index.php?module=channel&provider=Google§ion=news&article=something
I’m not sure which I prefer. The method mentioned in the article does give extra flexibility without having to modify the .htaccess, but the latter gives more specification as to how the URLs should work. I guess at the end of the day it’s up to opinion.
Just a quick simple reference point for me, as I am using this while I migrate websites from Tampa to Oblivion (Oblivion is not yet public, so I need Tampa to forward HTTP requests of websites that have moved onto Oblivion).
RewriteEngine on
RewriteCond %{HTTP_HOST} ^[a-zA-Z0-9.]*hostname.com$ [NC]
RewriteRule ^(.*)$ http://internal-hostname/$1 [P,L]
Note that this needs mod_proxy as well as mod_rewrite to be enabled.
Something I’ve not really played around with but I may do in the near future…. a very helpful info page about Apache’s mod_rewrite stuff:
http://corz.org/serv/tricks/htaccess2.php
An old article appeared in my phpdeveloper.org inbox today, about Microsoft and Zend uniting to improve Windows running PHP support. A chap called Tony Bibbs raised a question back then which I think could still be unanswerable, seeing as Microsoft’s bid to buy Yahoo! still hasn’t been accepted.
Read the rest of this entry »
