Either one works. Allowing .htaccess files has performance implications, since a filesystem scan must be performed and the config directives parsed every request. Using httpd.conf all that happens exactly once, at server startup.
..htaccess is really only for situations where you want people to be able to control certain aspects of the server config, without giving them access to the main configuration files, nor allow them to restart the Apache daemon. In other words, .htaccess is pretty much only for if you don't have access to httpd.conf. If there is a choice between the two, httpd.conf is the right one. cheers, barneyb On Thu, Jul 17, 2008 at 1:48 PM, Ian Skinner <[EMAIL PROTECTED]> wrote: > We need to create a couple of redirect directives for some moved content > on our websites. Do we have to create an .htaccess file for the > directory as all the documentation I have read alludes to or can we just > put the "redirect 301 /old/path/ /new/path" in the appropriate section > of the httpd.conf file? > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Adobe® ColdFusion® 8 software 8 is the most important and dramatic release to date Get the Free Trial http://ad.doubleclick.net/clk;203748912;27390454;j Archive: http://www.houseoffusion.com/groups/CF-Talk/message.cfm/messageid:309258 Subscription: http://www.houseoffusion.com/groups/CF-Talk/subscribe.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
