This is a continuation of my first article you can read here on how to use mod_rewrite with .htaccess. It can be a pretty daunting task getting all of this to work together seemlessly but once you get it working, it’s so easy and so sweet to use. In the last article
- How to enable .htaccess files
- How to include the mod_rewrite module in the httpd.conf (Apache Config)
- How to turn on .htaccess permissions in Apache config
- How to turn on mod_rewrite in a .htaccess file
- How to write mod_rewrite rules in .htaccess files
- How to create dynamic variables with preset tags
In this article we are going to handle a little more regex but also a little more of Apache’s built-in functionality.
Lets say you have a website, http://www.crainbandy.com and you want to accept anonymous commands to the “root” URL, or http://www.crainbandy.com/command instead of using a placeholder like we did in the last article. We used the placeholder cmd/commands.
What are placeholders?
When you begin to work with .htaccess files and mod_rewrite for your URI’s you’ll realize that you have to have a placeholder to extend your URLs off of, example
http://www.crainbandy.com/cmd/signup or http://www.crainbandy.com/cmd/login the placeholder here is cmd because it is familiar to you. You are already looking for this variable so there aren’t any surprises, everything after the placeholder is turned into the command and you can deal with it accordingly. After you have a working placeholder you extend with things like /functions or /send etc. Let your imagination take it’s places. I hope you understand placeholders for URLs they are really essential with mod_rewrite (until you get into heavy regex & apache voodoo which I don’t intend to get into in this article)
What if I just want to have /login instead of /cmd/login?
Good luck, not going to happen.
…just kidding.
Well that’s the problem I ran into. The reason this was particularly hard to find an answer for is because Apache automatically searches for a folder first, then a file. So if you go to crainbandy.com/login and it’s not a folder, nor a file, nor does apache have a rule to deal with this it just crashes giving you a 404 error… Hardly the desired result. So I, being the crafty being that I am thought about using a folder /login to hold the login script, but I just don’t want to have folders for all of my root URL functions (root URL meaning, right after the base url or www.crainbandy.com/THIS IS THE BASE AREA/THIS IS POST BASE/ THIS IS POST POST BASE… etc) so I thought ah well, what if I redirect the 404 to my index.php and parse it there? Cool. You just run into more problems so then I decided to stop being a genius and use Google & the Apache manual to find this
Enter the world of RewriteCond’s and RewriteRules working together in a harmoniously violent and tasty artistic jellyish fashion.
In english, you can tell apache “If there isn’t a folder, or a file, do this” which is exactly what we need, so here’s the code.
RewriteEngine on
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^([^/.]+)$ index.php?cmd=$1 [L]
Oh so nice. notice how the start of the rule … “^” doesn’t have a placeholder? like ^cmd or ^action it just simply has that scary regex statement that like I said in my previous post, says “everything”, isn’t that crafty? All of that !-d voodoo is built-in to Apache. Basically says, Find a filename or a folder … (-d) if you can’t find it, do the rewrite rule below. So! Hope that helps you guys some more! This would allow for what I call, base URI’s (actions & commands and all kinds of stuff without placeholders) which is sexy.
You could use this for a myspace type result with the whole, “myspace.com/users_url” thing. So, hope this helps you make your site a little bit cooler.
