An .htaccess file contains directives that the web server will apply to a collection of resources before a page is displayed. For example, a .htaccess file may change PHP configuration<\/a>, deny\u00a0access, change the page displayed, and even redirect a resource to another URL. These are denoted by a\u00a0directive<\/em>. A directive consists of a directive name and value, such as Before changing how the web server works, it’s important to know how these rules are applied. Before a request is processed, the server looks for a\u00a0 A page is served from\u00a0 Be careful with addon domain locations!\u00a0<\/em>.htaccess can be located under\u00a0 Create a plain-text file named\u00a0 You may also create an empty plain-text file within the control panel<\/a>\u00a0under Files<\/strong> >\u00a0File Manager<\/strong>.\u00a0You may then edit the file by clicking on\u00a0the\u00a0Edit<\/strong> action in the Actions<\/em> column\u00a0to make changes from your browser.<\/p>\n<\/blockquote>\n Each directive is one-line long and placed on a separate line. For example, these are all valid<\/em>\u00a0directives:<\/p>\n These are all invalid:<\/i><\/p>\n Sometimes a directive may be improperly entered into your .htaccess file. In such cases, the web site will fail to display and an\u00a0Internal Server Error<\/em>\u00a0will be generated. You can refer to\u00a0DirectoryOptions +Indexes<\/code> or\u00a0php_flag display_errors on<\/code>.<\/p>\nDirective precedence<\/h2>\n
<\/code>file called\u00a0.htaccess<\/code> in the directory in which content is served<\/a>. Any directives in this file are applied. The server will then backtrack down each directory until it reaches\u00a0\/var\/www<\/code> applying whatever directives are present in whatever .htaccess files it finds along the way.<\/p>\n\n
Example<\/h3>\n
\/var\/www\/mydomain.com<\/code>. .htaccess files are located present as\u00a0\/var\/www\/mydomain.com\/.htaccess<\/code> and\u00a0\/var\/www\/.htaccess<\/code>. First, rules in\u00a0\/var\/www\/mydomain.com\/.htaccess<\/code> are applied. Then, any rules in\u00a0\/var\/www\/.htaccess<\/code> are applied\u00a0overriding any rules present under\u00a0mydomain.com\/<\/code>.<\/p>\n\/var\/www<\/code> to apply global configuration to any subdomain or\u00a0domain located under\u00a0\/var\/www<\/code>.<\/p>\n<\/blockquote>\nSetting directives<\/h2>\n
.htaccess<\/code>\u00a0that will be uploaded in the document root<\/a> for the subdomain or domain whose behavior you would like to modify.<\/p>\n\n
\n
Options +Indexes<\/code><\/li>\nRewriteCond %{HTTPS} ^ON$<\/code><\/li>\nphp_value error_reporting 99999<\/code><\/li>\nPassengerEnabled On<\/code><\/li>\n<\/ul>\n\n
\n
<\/code>php_value error_reporting display_errors on\n\n
\n
\n
Handling Errors<\/h2>\n
error_log<\/a><\/code>\u00a0for a detailed explanation of what directive was rejected and for what particular reason.<\/p>\nCommon Directives<\/h2>\n