txt file issues and question

[askmediy]

I just noticed today that Google could not read my robots.txt . I tried other .txt files and none of them could be read.

I removed this from my .htaccess
RewriteRule ^(.*)(\.rss|\.atom|\.txt)$ index.php [L] And now .txt files can be read. Do I have something wrong here ?

This is my .httaccess file I'm using the newest Vivvo 4.5.2

RewriteEngine On
RewriteRule ^sitemap\.xml$ index.php [L]
RewriteRule ^(.*)(\.html|\.htm)$ index.php [L]
RewriteRule ^(.*)(\.rss|\.atom|\.txt)$ index.php [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)/?$ index.php [L]
RewriteRule ^robots.txt$ robots.txt [L]

[Alex]

Try like this:

RewriteRule ^sitemap\.xml$ index.php [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteRule ^(.*)(\.html|\.htm|\.rss|\.atom|\.txt)$ index.php [L]
RewriteCond %{REQUEST_FILENAME} !-f
RewriteCond %{REQUEST_FILENAME} !-d
RewriteRule ^(.*)/?$ index.php [L]

[askmediy]

Thanks Alex. Added RewriteEngine On to your code and works great thank you..

[zontech]

A couple of lists that might interest some Vivvo comrades.
http://www.javascriptkit.com/howto/htaccess13.shtml
http://www.askapache.com/htaccess/bl...-htaccess.html

But a question about huge .htaccess listing:

Some sites limit access to users only in their home country by including
zillions of IP address ranges. (An visitor with IP address in that range can't access the site.)

Does anyone have a very large .htaccess file which includes IP range exclusions AND a large bot-exclusion listing?

If so, do you notice any degradation in site performance?

Have had a scull around for this topic but not much found.

TIA

[sip]

Originally Posted by zontech

If so, do you notice any degradation in site performance?
TIA

.htaccess is always accompanies with a performance hit. If site is on a single tenant dedicated server best is to avoid .htaccess completely and achieve same thing in apache config:

http://httpd.apache.org/docs/2.2/how...cess.html#when

[zontech]

Crikey - it's more dire than I thought.

Have no choice but to use .htaccess for that client but have noted the advice you sent - very valuable info thanks.