dmorison - 5:23 pm on Jul 17, 2013 (gmt 0)
however, if you have another redirect in example.com's .htacccess you've got multiple hops, which could be avoided if you used a single VirtualHost and a ServerAlias.
But I don't, and never said I did!
I was suggesting two alternatives to the OP, an Apache configuration solution (my preferred option, if available, as it removes the requirement to process a canonical correction RewriteRule for every single page view, or a .htaccess solution otherwise.
If the .htaccess of the redirection destination happens to make another 301 redirect that is a separate issue, unrelated to the thread topic, and I agree, should be completely avoided!