There's no reason why the three lines above should not all work together, as long as the requested URL-paths to be redirected are all different from each other as shown.
So all I can really contribute is to point out that you must delete your browser cache before testing any new server-side code like this. Otherwise, you will likely see previously-cached pages and 'stale' server responses (such as redirects) from your browser's cache.
Do be aware that if any further path-info follows the URL-path prefixes specified above, then that path-info will be appended to the redirect target URL. For example, if racy.html
foobar is requested, then the redirect will go to http:
//b238emmcrjbr1m7dxbr9hbnd50.hop.clickbank.net/?tid=ez
foobar If this is NOT the desired function, then use RedirectMatch or RewriteRule instead of the Redirect directive.
Jim
[edited by: jdMorgan at 8:11 pm (utc) on Feb 7, 2011]