I don't think it's worth it at this point as the mod_rewrite alternative works and is more readily understood by everyone.
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.
I'm pretty sure there are plugins and hacks out there that rely on mod_rewrite
as well, which would break.
Moving between different versions of Apache would also break without the
ability for us to tell the user what broke.
Maybe when it's more widely adopted and deployed, but I don't think it's time
yet...
On Oct 26, 2010, at 2:32 PM, Rich Bowen wrote:
> FYI, as of Apache 2.2.16, the FallbackResource directive is available, and
> can replace our .htaccess file with one line:
>
> FallbackResource index.php
>
> It might be worth checking at install time to see if they're running 2.2.16
> or 2.4.x and use that instead of all that RewriteRule nonsense.
>
>
> --
> Rich Bowen
> [email protected]
> http://drbacchus.com/
>
>
>
> --
> To post to this group, send email to [email protected]
> To unsubscribe from this group, send email to
> [email protected]
> For more options, visit this group at
> http://groups.google.com/group/habari-dev
smime.p7s
Description: S/MIME cryptographic signature
