title: .ht access not working on Amazon linux server
body: <p>I've been working on a project that uses pushstate to manage site navigation. The project is currently hosted on a Godaddy shared hosting account and i've just setup an Amazon EC2 Linux server with HTTPD and have transfered the files across to the new server. I had to add a .htaccess file to help with the pushstate navigation so that it does not 404 when I try going to <a href="http://example.com/page1" rel="nofollow noreferrer">http://example.com/page1</a> for example. </p>
  
  <p>When I try and access a page like <a href="http://example.com/page1" rel="nofollow noreferrer">http://example.com/page1</a> on the godaddy server it behaves as it should - it does not try and access the actual page but instead uses the root page and appends url path /page1 and my javascript takes care of visually showing page1's content. However, on the Amazon server it is taking me to a 404 page. I'm fairly new to .htaccess and push state so I had to go off what I could find on stack overflow to help me get this working (on the Godaddy server at least). Here's the file:</p>
  
  <pre><code>RewriteEngine On
  RewriteRule ^([^/d]+)/?$ index.html?id=$1 [QSA]
  </code></pre>
  
  <p>Not sure if I have used the correct approach nor why one server would give me a different result to the other?</p>
  
  <p>Thanks</p>
  
  <p><strong>EDIT</strong></p>
  
  <p>So I have already set the allowOveride to all in my httpd.conf file as per below:</p>
  
  <pre><code>&lt;Directory "/"&gt;
      AllowOverride All
  &lt;/Directory&gt;
  </code></pre>
  
  <p>Worth noting here i'm using HTTPD rather than Apache2 - i'm not sure if this could make a difference or not but seems to be the same procedure. I also restarted the server using <code>sudo service httpd restart</code> but it's still the same result. I did try the vhost option and while I can't remember exactly what I wrote for it I had it apply to */80 so i'm fairly sure it was written correctly. </p>
  
  <p>Is there any other steps I can take to debug this further and try pin point exactly where it's going wrong?</p>