Rule #1: Use "www.example.com" in any, er, example that's preceded by http:// All other domain names change into clickable links. This is fine in other forums, but here we need to see what you typed
Does anything in your htaccess use mod_rewrite? If so, g1smd will be along shortly to tell you that you are taking your life into your hands when you mix mod_rewrite (Rewrite) and mod_alias (Redirect by that name) in a single htaccess file. Or config file or whatever you're in. You can use mod_rewrite to create redirects.
Meanwhile, we've got:
RedirectMatch 301 (.*)/store/buy/travel-size/womens2011/TBG762 http://www.example.com/store/bath-body/travel-size/womens2011/TBG884/
Oh, lord. For starters, you don't really need the http:// part unless you are redirecting to a different domain-- and your question gives no hint that this is the case. [httpd.apache.org
...] * says
The new URL should be an absolute URL beginning with a scheme and hostname, but a URL-path beginning with a slash may also be used, in which case the scheme and hostname of the current server will be added.
I prefer not
to give the full http business, because that makes it easier to distinguish at a glance between things that are being redirected to the same domain, and things that are going elsewhere.
Now then. How many different
pages do you have whose url contains the sequence /store/buy/travel-size/womens2011/TBG762
? Doesn't matter what comes after. How many different things can come before
this part? We're not talking /images/ or /includes/ here; that's a pretty detailed series of directories.
The (.*) is fairly disastrous in any case, but here it also isn't necessary. Get as specific as you can.
* A bit further along, they give as an example
RedirectMatch (.*)\.gif$ http://www.anotherserver.com$1.jpg
I know who did not
write this page of the documentation. Heh, heh.