NYCPHP Meetup

[Billy Reisinger]

So, yeah, there's the whole point about the urls being easier to  
remember.  Also, having your query string out there in the wild  
reveals some things about your implementation to would-be hackers.   
Not that you aren't covering your ass, of course. That's just another  
excuse I've heard for using mod-rewrite.
Another thing is that you aren't revealing the file type you are  
using (php) and thus are making it even harder for someone to know  
how you are generating content.  Of course, someone could just  
inspect the HTTP headers to find out your server is using PHP.  On  
the other hand, if you are using a service to distribute your content  
widely, like a server farm (think Akamai), you now have complete  
ambiguity about what technology you are using.

On Oct 3, 2006, at 7:45 AM, Richard Harding wrote:

> Cliff Hirsch wrote:
>> I’m confused by mod_rewrite
>>
>> What is the point? What is the big deal?
>>
>> Why is www.website.com/page/action/stuff/morestuff/
>>
>> Better than
>>
>> www.website.com/page.php?action=something&id=#&....
>>
>> What difference does it make? To me it mainly looks like a major
>> headache making all the queries written in PHP play nicely with  
>> mod_rewrite.
>
> Ever tried reading an email like the second over the phone?
>
> Rick
> _______________________________________________
> New York PHP Community Talk Mailing List
> http://lists.nyphp.org/mailman/listinfo/talk
>
> NYPHPCon 2006 Presentations Online
> http://www.nyphpcon.com
>
> Show Your Participation in New York PHP
> http://www.nyphp.org/show_participation.php