Editing .htaccess (section)

==Disadvantages==
Controlling Apache using the main server configuration file <kbd>[[httpd.conf]]</kbd><ref>{{cite web | url=http://httpd.apache.org/docs/current/configuring.html | title=Configuration Files - Apache HTTP Server | access-date=2008-01-12}}</ref> is often preferred for security and performance reasons:<ref>{{cite web|url=http://httpd.apache.org/docs/current/howto/htaccess.html#when |title=When Not to use .htaccess files |publisher=Httpd.apache.org |access-date=2009-09-02}}</ref>
; Performance loss: For each [[HTTP request]], there are additional file-system accesses for parent directories when using <kbd>.htaccess</kbd>, to check for possibly existing <kbd>.htaccess</kbd> files in those parent directories which are allowed to hold <kbd>.htaccess</kbd> files. It is possible to programmatically migrate directives from <kbd>.htaccess</kbd> to <kbd>httpd.conf</kbd> if this performance loss is a concern.<ref>{{cite web | url=http://blog.preinheimer.com/index.php?/archives/340-.htaccess-to-httpd.conf.html | title=How to convert .htaccess to httpd.conf entries}}</ref>
; Security: Allowing individual users to modify the configuration of a server can cause security concerns if not set up properly.<ref>{{cite web | url=http://httpd.apache.org/docs/current/misc/security_tips.html#systemsettings | title = Protecting System Settings | access-date=2009-03-02}}</ref>
; Syntax: <kbd>.htaccess</kbd> is usually very sensitive to syntax errors. Due to this any misspellings may lead to [[List of HTTP status codes#5xx_server_errors|server errors]] and web resources in the directory with the erroneous <kbd>.htaccess</kbd> not being displayed at all.