Force requests to a sub-directory

[Excalibur]

Hello,

I've been trying to for site.com/<whatever page is requested here> to site.com/dir/<whatever page is requested here>, but I seem to be out of luck.

here's my code:
RewriteCond %{HTTP_HOST} !site.com [NC]
RewriteRule (.*) [site.com...] [R=301,L]

Ideas?

Regards,

[Air]

make the necessary substitutions to directory, and domain, should work;

RewriteEngine ON
RewriteCond %{REQUEST_URI} !^/?directory
RewriteRule ^(.+)?$ http://example.com/directory/$1 [QSA,R=301]

[g1smd]

QSA is implied anyway. Omit it.

You need to add [L] always.

[Excalibur]

It worked great, thank you guys.

[jdMorgan]

A remaining question is whether you actually wanted a redirect, which exposes the new filepath as a URL to the client (and forces all the search engines to toss all your old URLs), or whether you simply want to move the files that those old URLs correspond to into a sub-directory, changing where the 'content' for those old URLs is stored, but not changing the URLs themselves.

If that's the case, then you want an internal rewrite, not an external redirect, and the code will need to be tweaked.

Jim

[Excalibur]

Jim,
I wanted an internal rewrite actually. And it worked (you gave me a great code in a previous post). But having the internal rewrite & that old code together didn't work.

And the new website has new contents, so what the search engines have will be different from what is there now anyway.
However, if you have a better solution, it would be so great to share
it.

[jdMorgan]

The usual problem when 'new code' doesn't work with 'old code' is that the new code has been inserted in the wrong place. See this concurrent thread, and look for the list I posted showing mod_rewrite rule-ordering [webmasterworld.com].

Jim

[Excalibur]

Jim,

Thanks again for the resource. I should take my time reading & trying things out. If I happen to not get it done properly, I shall ask again.

Thank you very much.

--Ex