On Jun 15, 2009, at 09:47, Realpolitik wrote:
> Lets pretend a very > generous 75% of Habari's potential user base has the ability to > rewrite URLs, it could have 33% more reach. I love making decisions based on made-up statistics. It's one of the things I love so much about my day job.</sarcasm> On my side of the fence, I'm fighting this battle with education. The only reason that folks *don't* have mod_rewrite enabled is ignorance, in which vacuum folks made up security myths and pretend that they're doing it for reasons of security and/or performance. If you have sysadmins who refuse to enable mod_rewrite for reasons that seem spurious, please feel free to give them my phone number. I'd be glad to talk with them about their concerns, and help them eliminate those concerns. In this age, mod_rewrite is an essential part of the Apache Web Server, and folks that have it disabled are crippling their customers. This is a pretty simple business decision. Enable mod_rewrite, or folks will eventually move to a provider that will. Unfortunately, there's an ENORMOUS amount of misinformation out there about mod_rewrite, and a lot of ignorant people pushing "tips and tricks" that are misleading or just plain wrong. On the Apache documentation project, we've been actively fighting this for about three years. And some of the improvements in Apache 2.4 make entire classes of rewrite rules unnecessary. And I'm still holding on to the hope that https://issues.apache.org/bugzilla/show_bug.cgi?id=47184 will get implemented, and this issue will go away - at least for folks that move to Apache 2.4. -- Whatever you do will be insignificant, but it is very important that you do it. Mahatma Ghandi --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/habari-dev -~----------~----~----~----~------~----~------~--~---
