httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [Bug 56883] multiviews option causes a fail in ModRewrite
Date Sun, 24 Aug 2014 18:28:57 GMT

--- Comment #4 from Eugenia Bahit <> ---
(In reply to Eric Covener from comment #3)
> It's difficult to follow what your expectation or even observations are for
> the interaction between the two modules when both are enabled.  A more
> self-contained example would help.
> Do things work better more as you expect if your rewriterules are not in
> htaccess/directory context?

I'm sorry. My english is not good. I'm not sure if understand your answer but I
will try to explain the problem again with an example.

Until Apache 2.4, if you put at your VirtualHost the following instructions:
<Directory /path/to/application/root>
    Options -Indexes FollowSymLinks MultiViews
    RewriteEngine On
And then, in the .htaccess of /path/to/application/root writing this rule:

RewriteEngine On
RewriteRule ^ controller.php

All, absolutely all petitions go to controller.php without exceptions.

Since Apache 2.4 the same instructions and the same rewrite rules at the same
places causes that all petitions go to controller.php but with some exceptions.
By example:

Until Apache 2.4, /something-like-that go to controller.php always.

Since Apache 2.4, /something-like-that go to controller.php if not exists a
file called something-like-that (.something like .php or .html, etc).

If exists a file called something-like-that, Apache 2.4.x generates an error
404 not found. But if you entering /something-like-that.extension in the URL,
go to something-like-that.extension instead of controller.php

You are receiving this mail because:
You are the assignee for the bug.

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message