Jump to content


mod_rewrite vs. custom php solution for handling accessible URLs?

  • Please log in to reply
1 reply to this topic

#1 mmosel

  • Members
  • PipPipPip
  • Advanced Member
  • 66 posts

Posted 10 July 2006 - 09:22 PM

I've read some articles on using PHP to process accessible URLs, and I'm also aware that a lot of people use mod_rewrite for this. So, what's the difference really? If you do this with your site, what solution do you use?

#2 willfitch

  • Members
  • PipPipPip
  • Advanced Member
  • 109 posts
  • LocationNew Hope, PA

Posted 11 July 2006 - 03:03 AM

It really depends on your access to modifying configurations.  If you have access to the httpd.conf or have AllowOveride set to All in your shared hosting configuration, mod_rewrite is the easiest, and typically safest solution.  Why do I say safest?

Simply put, as a developer, it's easy to make mistakes.  You will have to code overhead to parse the URL and get the strings needed to present data/content to the browser.  Also, if you aren't careful, you could be a good candidate for SQL injections.  What's the biggest reason to use mod_rewrite?  IT'S ALREADY WRITTEN!  Reuse the capabilities that are at hand, rather than coding everything from the hip.  Mod_rewrite is very efficient, and can do way more than you probably know. 

Give it a shot!
Zend Certified Engineer (ZEND001989)

0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users