Php – .htaccess send requests to a subfolder’s index.php

.htaccessmod-rewritePHP

I have searched StackOverflow for my answer, but nothing that I have seen seems to work.

I have a framework that sends all requests to an index.php file. Everything works when I install it in the root of the virtual host:

http://example.com/
http://example.com/home
http://example.com/home/index

The problem happens when I try to install the framework in a subdirectory like:

http://example.com/blog/

Requests like:

http://example.com/blog/home
http://example.com/blog/home/index

All of those requests should be sent to the index.php file that lives in /blog

My current set up is:

http://example.com/index.php – This file just prints out "we are in the root of the virtual host". The framework is not installed there.

http://example.com/blog – This works fine

When I try to get to http://example.com/blog/home I get the root index.php file, not the frameworks. I get the message "we are in the root of the virtual host".

I have the following .htaccess file located at http://example.com/blog/.htaccess.

RewriteEngine on

Options Indexes FollowSymLinks -MultiViews

RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule !\.(js|ico|gif|jpg|png|css)$ index.php

Any help is greatly appreciated.

Best Answer

The answer that fixed my problem is:

RewriteEngine On

Options Indexes FollowSymLinks

RewriteBase /blog/
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule !\.(js|ico|gif|jpg|png|css)$ index.php

It appears that the Multiviews was throwing it off.

Related Solutions

Rewrite rule does not rewrite url as expected

You can try this one, is working on my websites

RewriteRule ^([0-9]+)$ /index.php?id=$1 [L,QSA]

.htaccess rewriterule if/else

What you are trying to achieve is possible with both, and your currently working configuration is the traditional way of doing this. That's why there's plenty of examples for doing this with RewriteCond. The Expressions and directives If, ElseIf, Else and were introduced in Apache 2.4 as a long-awaited feature, and one of the first examples is to make rewriting more readable and predictable:

Some of the things you might use this directive for, you've been using mod_rewrite for up until now, so one of the side-effects of this directive is that we can reduce our reliance on mod_rewrite's complex syntax for common situations. Over the coming months, more examples will be added to the documentation, and we'll have a recipe section with many of the same sorts of scenarios that are in the mod_rewrite recipe section.

In fact, most of the commonest uses of mod_rewrite can now be replaced with the If directive, making them easier to read, and, therefore, less prone to error, and the redirect looping that so often plagues RewriteRule-based solutions.

Without testing, I'd say that using regular expressions with your use case makes this overly complicated. Because you are comparing Host: headers probably within a fixed domain, say example.com, you could use simple == (string equality) comparison operator instead of =~ (string matches the regular expression):

<ifModule mod_rewrite.c>
    RewriteEngine on
    <If "%{HTTP_HOST} == 'helpdesk.example.com'">
        RewriteRule ^/?$ /index.php?pages=helpdesk&file=index [NC,L,QSA]
    </If>
    <If "%{HTTP_HOST} == 'account.example.com'">
        RewriteRule ^/?$ /index.php?pages=account&file=index [NC,L,QSA]
    </If>
</ifModule>

Related Topic