.htaccess send requests to a subfolder's index.php

Question

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://domain/
http://domain/home
http://domain/home/index

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

http://domain/blog/

Requests like:

http://domain/blog/home
http://domain/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://domain/index.php - This file just prints out 'we are in the root of the virtual host' The framework is not installed there.

http://domain/blog - This works fine

When I try to got to http://domain/blog/home I get the roots 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://domain/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.

Regards,

Justin

Answer 1

RewriteRule !\.(js|ico|gif|jpg|png|css)$ index.php

Means "if not js or ico..." forward to index.php.

So, in essence, your /blog level htaccess is saying if it's not an image or CSS file redirect it to /blog/index.php

Answer 2

RewriteBase /blog

Try it without the forward slash.

Answer 3

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.

Answer 4

Do you know of anyway with htaccess to disable someone from using your domain to point to their own website on the same server? Ex: they use YOURDOMAIN.com to promote their PHISHING WEBSITE.COM by using this simple URL to send users : YOURDOMAIN.COM/~phishing/file.html

Any help would be greatly appreciated. Thanks

Answer 5

Are the requests that you're testing with for items that don't actually exist in the directory? These lines:

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

Mean that any requests for a file or directory that exists won't be rewritten.