Treating index and index.php as the same file

Question

I'm working on a PHP project using Apache 2.2.22 and PHP 5.3.10 and I'm running into an issue where index and index.php are being treated as the same file.

I have an admin/index.php that redirects to admin/index to allow my mod_rewrite rules in .htaccess to take over and reroute the request into a custom framework. The problem is, when the browser goes to admin/index it goes into an infinite redirect loop because the request is being sent to admin/index.php which redirects to admin/index

I've tried removing the htaccess file to see if there was a problem with my mod_rewrite rules that was causing it and it didn't change anything. It just redirects to admin/index endlessly.

I've never heard of this behavior before, skimming over some Google results and skimming through the apache configuration files didn't show anything really obvious. Has anyone seen this before and know how to fix it?

EDIT: Below is the code being used by the index.php to redirect to index.

<?php
    header("Location: index");
    die();

Are you saying you have an index.php and a directory called index? — DaveRandom
– DaveRandom, Commented Jun 26, 2012 at 22:08
this could be related, but I'm also curious about your DirectoryIndex setting... — Wrikken
– Wrikken, Commented Jun 26, 2012 at 22:09
It's not default behavior in Apache or PHP so I suspect there is another set of rewrite rules or redirects set up elsewhere, maybe in httpd.conf or the httpd-vhosts.conf file? Or you may have a .htaccess file in a parent directory that is still taking precedence over the one you removed which didn't solve the problem. — drew010
– drew010, Commented Jun 26, 2012 at 22:12
Post your php redirect code please. I've seen something similar if the redirect to a directory does not contain the final forward-slash. — K.B.
– K.B., Commented Jun 26, 2012 at 22:14
There is not a directory called index in admin/ and I'm using the stock configuration settings from Ubuntu's package with the only modification being a change to the document root. — chrisbdaemon
– chrisbdaemon, Commented Jun 27, 2012 at 13:43

Sam Wilson · Accepted Answer · 2013-01-07 07:42:25Z

1

This may be due to MultiViews being enabled:

The effect of MultiViews is as follows: if the server receives a request for /some/dir/foo, if /some/dir has MultiViews enabled, and /some/dir/foo does not exist, then the server reads the directory looking for files named foo.*, and effectively fakes up a type map which names all those files, assigning them the same media types and content-encodings it would have if the client had asked for one of them by name. It then chooses the best match to the client's requirements.

— https://httpd.apache.org/docs/2.2/content-negotiation.html#multiviews

Try adding Options -MultiViews to your .htaccess

answered Jan 7, 2013 at 7:42

Sam Wilson

4,5224 gold badges33 silver badges31 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

arkascha · Accepted Answer · 2012-06-26 22:11:29Z

0

Enable rewrite Logging inside Apache and raise the log level. That way apache will tell you exactly, step by step, what request is rewritten how, in which order and why.

answered Jun 26, 2012 at 22:11

arkascha

43.2k8 gold badges61 silver badges97 bronze badges

Collectives™ on Stack Overflow

Treating index and index.php as the same file

2 Answers 2

Comments

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related