On Oct 26, 2010, at 9:26 PM, Rich Bowen wrote:
>
> On Oct 26, 2010, at 4:07 PM, Chris Meller wrote:
>
>>
>> We include 2 lines for limiting the types of requests that do or don't
>> 'fallback':
>> RewriteCond %{REQUEST_URI} !=/favicon.ico
>> RewriteRule ^(system/(classes|locale|schema|$)) index.php [PT]
>>
>> Which I don't believe we could replicate with FallbackResource.
>
> Actually, that's exactly what FallbackResource does do.
The Apache mod_dir documentation [1], of which FallbackResource belongs,
mentions it as a substitute only for the mod_rewrite -f and -d lines that are
standard. I don't see how we would duplicate these 2 lines.
>
>>
>> I'm pretty sure there are plugins and hacks out there that rely on
>> mod_rewrite as well, which would break.
>>
>
> No, they wouldn't break at all, because this does exactly what that rule
> does, just more efficiently.
You misunderstand I believe. I'm referring to plugins that provide their own
mod_rewrite rules or hacks that users may manually use. FallbackResource,
assuming it would even work in our situation, would replace mod_rewrite and
make it difficult to juggle the two.
> I'm not suggesting that we do this immediately. I mention it merely because
> when I brought up FallbackResource on IRC about a year ago, people were
> excited by it, and it's finally been backported to 2.2.x
It's quite exciting, but unfortunately it doesn't seem like it's exactly what I
expected or remember... We do more than simply pipe non-existent files and
directories to index.php, so it doesn't seem like FallbackResource would be of
any use to us.
[1]: http://httpd.apache.org/docs/trunk/mod/mod_dir.html#fallbackresource
smime.p7s
Description: S/MIME cryptographic signature
