That will only redirect a request for the /oldfolder folder itself, and not for any files inside that folder.

Assuming that this code is in httpd.conf, try:

RewriteRule ^/oldfolder[b]/(.*)$[/b] http://www.example.com/newfolder[b]/$1[/b] [R=301,L]

The $1 in the substitution URL on the right back-references (takes the value of) the requested URL-path substring matching the parenthesized subpattern on the left. In this way, all files in /oldfolder are redirected to the same-named files in /newfolder.

For more information, see the documents cited in our forum charter [webmasterworld.com] and the tutorials in the Apache forum section of the WebmasterWorld library [webmasterworld.com].

Jim

Ahh, awesome. I never did understand those 2 variables. Works great.

My last question would be, why doesn't it actually rewrite the url? I mean, the only reason I would care is for SEO reasons..Not sure if it even matters though. The url still shows oldfolder in the address bar, yet it definitely redirected to newfolder....

If it redirected then the new URL should show. The [R=301] forces the browser to request the new URL in a new HTTP transaction.

On the other hand, a rewrite pulls content from the new location while showing the old URL. A rewite is almost the same code but without the [R=301] bit.

The code above is a redirect, and will change the browser address bar. But you must always completely flush your browser cache before testing any change to your configuration code.

In this case, if /oldfolder/foo.html is cached in your browser and you request it again, the browser will render that page from its cache, and no request will be sent to your server. Therefore, the rule can have no effect.

Jim

Cache it was. All works awesome now. Thanks!