Here's what I've got right now:
RewriteEngine On
RewriteBase /
RewriteCond %{REQUEST_URI} ^/stats/(.*)$ [OR]
RewriteCond %{REQUEST_URI} ^/failed_auth.html$
RewriteRule ^.*$ - [L]
#The Fix
http://meta.wikimedia.org/wiki/Using_a_very_short_URL#The_Fix
RewriteRule
^[^:]*\.(php|src|jpg|jpeg|png|gif|bmp|css|js|inc|phtml|pl|ico|html|shtml)$ -
[L,NC]
RewriteRule ^index.php?title - [L]
RewriteRule ^(.*)\&(.*)$ $1\%26$2
RewriteRule ^(.+)$ /index.php?title=$1 [L,QSA]
Options FollowSymLinks
RewriteEngine On
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.+)$ /index.php?title=$1 [L,QSA]
The strange thing is that other files remain accessible: My favicon and an
HTML form I have uploaded can still be reached normally. This seems to be
affecting only text files: I created a file called foo.html and could reach
it, but foo.txt redirected to Foo.txt.
On 4/8/07, Rob Church <robchur(a)gmail.com> wrote:
On 08/04/07, Emufarmers Sangly <emufarmers(a)gmail.com> wrote:
Anyway, things worked fine with this for a while,
until recently, I
noticed
that the robots.txt file for my domain wasn't
accessible: It had been
the
last time I checked, so I have to assume that a
software upgrade changed
something here. Does anyone know a way I could kludge (through
.htaccess,
or whatever) robots.txt (and sitemap.txt) into
being accessible, without
changing the root structure?
Your rewrite rule is likely rewriting everything in the root
namespace, which is one of the reasons we strongly recommend not
filling up your root namespace in this manner. You may or may not be
able to get away with some kludges to prevent rewriting cases such as
robots.txt.
Rob Church
_______________________________________________
MediaWiki-l mailing list
MediaWiki-l(a)lists.wikimedia.org
http://lists.wikimedia.org/mailman/listinfo/mediawiki-l
--
Emufarmers Sangly
Pirate, Cowboy,
Hellraiser