Re: 404 redirects "stolen" by provider

Am 09.04.2010 23:15, schrieb Peter Lind:

On 9 April 2010 23:08, Merlin Morgenstern<merlin_x@fastmail.fm> wrote:

Am 09.04.2010 22:58, schrieb Peter Lind:

     
On 9 April 2010 22:20, Merlin Morgenstern<merlin_x@fastmail.fm>    wrote:

       
This sounds like the best solution to me. The only problem is that my

regex knowledge is pretty limited. The command: RewriteRule ^(.+) /subapp_members/search_user.php

The above rule will try to redirect everything to /subapp_members/search_user.php. If you're looking to allow example.com/username, then use something like: RewriteCond %{REQUEST_FILENAME} !-f RewriteCond %{REQUEST_FILENAME} !-d RewriteRule ^(.*)$ /subapp_members/search_user.php?member=$1 [L] This is likely to not do what you want from it, but it's the closest I can guess as to what you want. Have a read of http://httpd.apache.org/docs/2.2/mod/mod_rewrite.html

This will not work, as I do have a bunch of other redirects inside the page. What might work is a rule, that redirects urls that do not have a full stop or slash inside. Is this possible? My regex knowledge is unfortunatelly pretty limited.

     Try:

RewriteRule ^([^./]+)$ /yourfile.php?variable=$1 [L] Apart from that, rewrite rules work in order. If a rule above this triggers and has the L flag, those below won't get processed. Hello Peter, thank you for the rewrite rule. This workes perfectly!! The other ideas like sending 200 afterwards did not work as 404 has already been sent. Thank you for you help! Merlin