Htaccess and mod_rewrite conditions?

Remove negation from the conditions and tell it to not to try and match the rewriterules if its a file or directory. Think that should work.

RewriteCond %{REQUEST_FILENAME} -f RewriteCond %{REQUEST_FILENAME} -d RewriteRule . €“ S=2 RewriteRule ^(.+)\.(\d+)\.(css|js)$ $1. $3 L RewriteRule ^.

*$ /errors/error. Php L remove negation from the conditions and tell it to not to try and match the rewriterules if its a file or directory. Think that should work.

This doesn't work. Apache terminates with a 500. – Zarathos Dec 7 at 3:57.

RewriteRule ^(.*)$ $1. Php This will redirect "/something-page" to "/soemthing-page. Php", which will then in turn hit this: RewriteRule ^something-page\.

Php$ /something-page R=301,L Place the something-page rule above the generic . Php rewrite rule, and mark it L.

Thanks Drew, tried that - but to no avail I'm afraid. It still chokes on the URI. – dikjones Mar 2 '10 at 22:00 So put the rewrite rule to the top - and marked it L.

Still to no avail, seems to still process the generic ^(.*)$ $1.php. Essentially google has indexed some of my /foo. Php pages, which I'd obviously like to redirect 301 to /foo - but I can't seem to get the rule to work as expected.

Any help, would be much appreciated. – dikjones Mar 9 '10 at 21:16.

I cant really gove you an answer,but what I can give you is a way to a solution, that is you have to find the anglde that you relate to or peaks your interest. A good paper is one that people get drawn into because it reaches them ln some way.As for me WW11 to me, I think of the holocaust and the effect it had on the survivors, their families and those who stood by and did nothing until it was too late.