Apache/2.4.6 update causes 404s

apache-2.4mod-rewrite

I'm running a ec2 ubuntu instance, I decided to update my PHP today to 5.5.7, unfortunately it triggered apache to update as well, which has caused me many errors, the biggest one is my rewrite rules are no longer being hit and I believe its something todo with .conf changes.

My site conf (yes my front and backend site share the same .conf, somewhat lazy but was convenient.

<VirtualHost *:80>
  DocumentRoot /var/www/hivetracking-front/checkout/hive-tracking/public/
  ServerName hivetracking.com
  ServerAlias www.hivetracking.com
  SetEnv _ENV production

        <Directory />
                DirectoryIndex index.phtml
                RewriteEngine On
                LogLevel alert rewrite:trace6
                Options Indexes FollowSymLinks
                AllowOverride All
        </Directory>


        ErrorLog /var/www/hivetracking-front/error.log


        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn
        CustomLog /var/www/hivetracking-front/access.log combined
</VirtualHost>

<VirtualHost *:80>
  DocumentRoot /var/www/hivetracking-back/checkout/hive-tracking-api/public
  ServerName api.hivetracking.com
  SetEnv _ENV production

        <Directory />
                DirectoryIndex index.php
                RewriteEngine On
                LogLevel alert rewrite:trace6
                Options Indexes FollowSymLinks
                AllowOverride All
        </Directory>


        ErrorLog /var/www/hivetracking-back/error.log

        # Possible values include: debug, info, notice, warn, error, crit,
        # alert, emerg.
        LogLevel warn
        CustomLog /var/www/hivetracking-back/access.log combined
</VirtualHost>

My .htaccess for the API:

RewriteEngine on
ServerSignature On
DirectoryIndex index.php
Options Indexes FollowSymLinks


<FilesMatch "\.(ico|pdf|flv)$">
    Header set Cache-Control "max-age=29030400, public" #1 YEAR
</FilesMatch>
<FilesMatch "\.(xml|txt|css|jpg|jpeg|png|gif|swf)$">
    Header set Cache-Control "max-age=172800, proxy-revalidate" #1 WEEK
</FilesMatch>
<FilesMatch "\.(html|htm|php|js)$">
    Header set Cache-Control "max-age=60, private, proxy-revalidate" #2 DAYS
</FilesMatch>


# system/session
RewriteRule ^([-A-Za-z0-9]+)/([-A-Za-z]+)$ index.php?__module=$1&__action=$2 [L,QSA]

# teams/something/123456
RewriteRule ([-A-Za-z0-9]+)/([-A-Za-z0-9]+)/([0-9a-fA-F]{24}+)$ index.php?__module=$1&__action=$2&id=$3 [L,QSA]

# teams
RewriteRule ^([-A-Za-z0-9]+)$ index.php?__module=$1&__action=index [L,QSA]

# teams/123456
RewriteRule ([-A-Za-z0-9]+)/([0-9a-fA-F]{24}+)$ index.php?__module=$1&__action=index&id=$2 [L,QSA]


RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d

Going to http://api.mydomain.com/client results in a 404
Going to http://api.mydomain.com/index results in a 404
Going to http://api.mydomain.com/index.php loads the file

Any help greatly appreciated!

EDIT

I fixed this by removing these from the .htaccess

<FilesMatch "\.(ico|pdf|flv)$">
    Header set Cache-Control "max-age=29030400, public" #1 YEAR
</FilesMatch>
<FilesMatch "\.(xml|txt|css|jpg|jpeg|png|gif|swf)$">
    Header set Cache-Control "max-age=172800, proxy-revalidate" #1 WEEK
</FilesMatch>
<FilesMatch "\.(html|htm|php|js)$">
    Header set Cache-Control "max-age=60, private, proxy-revalidate" #2 DAYS
</FilesMatch>

I have no idea why it took me 8 hours of debugging to track this down but the errors weren't being logged.

Best Answer

Search your configuration files for all examples of AllowOverride. Likely something that has been added which is replacing the one in your config above.

Second, in your config for the VirtualHost, replace the Directory statement with your document root:

    <Directory /var/www/hivetracking-front/checkout/hive-tracking/public>
            DirectoryIndex index.php
            RewriteEngine On
            LogLevel alert rewrite:trace6
            Options Indexes FollowSymLinks
            AllowOverride All
    </Directory>

This will help assure something else is not overriding the AllowOverride Setting.

Related Solutions

Tomcat – Apache2 – mod_expire and mod_rewrite not working in httpd.conf – serving content from tomcat

Probably the ProxyPass / directive you have in your config routes all requests to the Tomcat backend, bypassing all your mod_rewrite directives. You can try to remove the ProxyPass directive and use RewriteRule with the [P] flag after your other rewrites:

mod_rewrite: P|proxy

For the expire headers the situation is worse — in another similar question a solution was not found.

Option +FollowSymLinks would be needed for using mod_rewrite in .htaccess files; in your case it is not required, because you can put everything in the Apache config. Moving rules from config to .htaccess is pointless and can only make things slower. However, there is an important difference between .htaccess and the Apache config — in .htaccess patterns in RewriteRule are matched against relative filesystem paths (which never start with /), while in the VirtualHost context these patterns are matched against the URL path after the hostname, which always starts with /. Therefore at least one of your rules is incorrect:

RewriteRule ^content/(js|css)/([a-z]+)-([0-9]+)\.(js|css)$ /content/$1/$2.$4

should be

RewriteRule ^/content/(js|css)/([a-z]+)-([0-9]+)\.(js|css)$ /content/$1/$2.$4

(note the additional slash in the beginning).

Apache encoding URI causing 404s

A hypothesis...

RewriteRule .* index.php?request=$1 [L,QSA]

This line looks like an error, since the $1 backreference will always be empty as there is no captured group in the RewriteRule pattern.

The "framework" may still work (for the Latin alphabet) because it may be parsing the $_SERVER['REQUEST_URI'] PHP superglobal instead (as a fallback perhaps) - which many frameworks do. However, $_SERVER['REQUEST_URI'] will remain URL encoded (eg. /actor/%C3%85ker) - so this probably needs to be URL decoded (eg. /actor/Åker) before it can be routed through your framework. This might be where the problem is. A request like /actor/Aker, on the other hand, is the same whether it's URL encoded or not, so this would not affect URLs like this.

However, if your framework allows the requested URL to be overridden with the request URL parameter then consider changing the above directive to:

 RewriteRule (.*) index.php?request=$1 [L,QSA]

ie. enclose the RewriteRule pattern in parentheses.

This will result in the captured URL-path being passed in the request URL parameter. Now, the important difference with this is that the URL-path that the RewriteRule directive matches against is already URL decoded. So, the request URL parameter already contains the URL-decoded request (albeit less the slash prefix), eg. actor/Åker.

UPDATE: Try changing the RewriteRule pattern from .* to [\s\S]* instead. For example:

 RewriteRule ([\s\S]*) index.php?request=$1 [QSA,L]

This is just a slightly more encompassing pattern. Whilst . (dot) matches any-character (excluding newlines), [\s\S] matches any whitespace and any non-whitespace characters (ie. everything).

EDIT

Best Answer

Related Solutions

Tomcat – Apache2 – mod_expire and mod_rewrite not working in httpd.conf – serving content from tomcat

Apache encoding URI causing 404s

Related Topic