On Thu, Apr 9, 2009 at 1:22 AM, Velda <[email protected]> wrote: > http://billing.handsonwebhosting.com/knowledgebase.php?action=displayarticle&id=132
To summarize, in case there is still any confusion: "RedirectPermanent" is just an alias for "Redirect permanent". According to http://httpd.apache.org/docs/2.0/mod/mod_alias.html#redirect The default return code for Redirect is 302 (temporary), changing this to 301 (permanent) is really simple. When using mod_rewrite specifying [R=301,L] causes mod_rewrite to use the 301 return code instead of the 302. The client sees the exact same result with mod_rewrite as using Redirect. In regards to performance, having very large configuration files causes more performance problems than simple mod_rewrite rules. Unless you disable the entire mod_rewrite module from Apache, you will not see much performance gain for not using it over Redirect. The primary performance hit to mod_rewrite is the loading of the module itself during forks. The rule processing performance hit is so small it will not be a bottleneck until you reach Google proportions. Also, in regards to over-optimization, don't focus on minute performance gains that cause you additional pains/administration until you reach that point. You'll end up costing yourself more in the long run. Value your time. How much money have you cost your employer already researching this issue? If, and hopefully when, you reach scaling issues, you can then consider other methods and change. --lonnie _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
