Actually, I've made a mistake, but not the one you think.
"www.weissbrod.com" (or "weissbrod.com") is a site on its own (I've made it, BTW, that the latter redirects to the former via the same mod_rewrite method in .htaccess).
"lior.weissbrod.com" is a subsite of that domain, but the ISP's server is smart enough to make it virtually a stand alone site (it has its own robots.txt, .htaccess, etc.).
However - and here lies the problem - it wasn't always like that. Before my ISP upgraded to their smart server, I've had to resort to a little CGI script (called "DomainDirector") that just made a simple redirect to "www.weissbrod.com/lior".
To make things even more complicated, during that time a new version of that CGI script soon came out and made it look better by redirecting it to "lior.weissbrod.com/lior" (the first "lior" is fake.
Unlike now, the "subsite" was still "www").
...So when I've quoted my .htaccess in the previous post (after upgrading it using your suggestion), I only fixed the "www.weissbrod.com/lior" problem!
Alas, since the new version of that CGI script came almost as soon as I've started to use the script in the first place, that version of the site didn't last long - so it barely matters anyway (only 1 match in Google...).
The big problem is "lior.weissbrod.com/lior" and my .htaccess currently has no solution for that.
But since I no longer use "/lior/", every page that Google has with it throws back a 404 message!
This time don't blame me - Google's own FAQ states that
"you don't need to bother us to remove your pages - just throw back 404 messages!"Yet it has been a long time now and tons of "/lior/" pages still show up!
So my question is this - should I just give up on those 404 messages and use
Text Formatted Code
RewriteCond %{HTTP_HOST} !^lior\.weissbrod\.com$ [NC,OR]
RewriteCond %{REQUEST_URI} ^/lior/ [NC]
RewriteRule ^.*$ http://lior.weissbrod.com/ [R=permanent,L]
?
In other words, 404 (like Google supposedly wants, but doesn't seem to respect) or 301?