{"id":1587,"date":"2013-03-28T09:42:14","date_gmt":"2013-03-28T09:42:14","guid":{"rendered":"http:\/\/blog.designed79.co.uk\/?p=1587"},"modified":"2013-03-28T09:42:14","modified_gmt":"2013-03-28T09:42:14","slug":"ubuntu-apache2-enable-htaccess","status":"publish","type":"post","link":"https:\/\/blog.designed79.co.uk\/?p=1587","title":{"rendered":"Ubuntu Apache2 enable .htaccess"},"content":{"rendered":"
\n

EnablingUseOfApacheHtaccessFiles<\/a><\/h1>\n<\/div>\n
\n
\n<\/div>\n
\n
\n
\n

WARNING<\/strong>: This page was written based on Ubuntu 10.04 (Lucid), although the same may apply to other releases. You are encouraged to also read:<\/p>\n

    \n
  1. The related\u00a0ubuntu server guide<\/a>\u00a0(Choose your distribution version > “Ubuntu Server Guide” > “Web servers”).<\/li>\n
  2. The apache htaccess tutorial:\u00a0http:\/\/httpd.apache.org\/docs\/2.0\/howto\/htaccess.html<\/a><\/li>\n<\/ol>\n

    By\u00a0default<\/strong>, Ubuntu’s Apache will\u00a0ignore<\/strong>\u00a0the directives in your\u00a0.htaccess<\/tt>\u00a0files.<\/p>\n

     <\/p>\n

    When (not) to use .htaccess files<\/h2>\n

    According to\u00a0Apache.org’s Apache Tutorial<\/a>,<\/p>\n

    “In general, you should never use .htaccess files unless you don’t have access to the main server configuration file. There is, for example, a prevailing misconception that user authentication should always be done in .htaccess files. This is simply not the case. You can put user authentication configurations in the main server configuration, and this is, in fact, the preferred way to do things.”<\/em><\/p>\n

    “.htaccess files should be used in a case where the content providers need to make configuration changes to the server on a per-directory basis, but do not have root access on the server system. In the event that the server administrator is not willing to make frequent configuration changes, it might be desirable to permit individual users to make these changes in .htaccess files for themselves.”<\/em><\/p>\n

    On Ed\/X\/Ubuntu 6.06 and Ubuntu Edgy Eft, the\u00a0“main server configuration file”<\/em>\u00a0is\u00a0\u00a0\/etc\/apache2\/apache2.conf\u00a0<\/tt>.<\/p>\n

     <\/p>\n

    OK, I know it is not recommended — how do I do it anyway?<\/h2>\n

    To make\u00a0.htaccess<\/tt>\u00a0files work as expected, you need to edit this file:<\/p>\n

    \/etc\/apache2\/sites-available\/default<\/pre>\n
    Look for a section that looks like this:<\/p>\n
            <Directory \/var\/www\/>\r\n                Options Indexes FollowSymLinks MultiViews\r\n                AllowOverride None\r\n                Order allow,deny\r\n                allow from all\r\n                # Uncomment this directive is you want to see apache2's\r\n                # default start page (in \/apache2-default) when you go to \/\r\n                #RedirectMatch ^\/$ \/apache2-default\/\r\n        <\/Directory><\/pre>\n
    You need to modify the line containing\u00a0AllowOverride\u00a0None<\/tt>\u00a0to read\u00a0AllowOverride\u00a0All<\/tt>. This tells Apache that it’s okay to allow.htaccess<\/tt>\u00a0files to over-ride previous directives. You must\u00a0reload<\/em>\u00a0Apache before this change will have an effect:<\/p>\n
    sudo \/etc\/init.d\/apache2 reload<\/pre>\n
    2009.12.08 note: in the LAMP download about a week ago with Ubuntu 9.10 (Karmic) the default configuration file was\u00a0\/etc\/apache2\/sites-available\/000-default<\/tt>\u00a0and it included\u00a0AllowOverride<\/a>\u00a0None under\u00a0<Directory\u00a0\/><\/tt>\u00a0in addition to\u00a0<Directory\u00a0\/var\/www\/><\/tt>. Also, directories in\u00a0\/www\/var\/<\/tt>\u00a0containing\u00a0.htaccess<\/tt>\u00a0files defaulted to not giving the Apache server read access, resulting in the Apache error<\/p>\n