phranque - 5:55 am on Apr 20, 2013 (gmt 0)
For what it's worth, the Apache documentation can weigh in.httpd.apache.org/docs/trunk/rewrite/avoid.html#redirect
It says your way is better. happy! mod_rewrite is actually supposed to be a last resort in favor of other directives designed to do a specific job (like redirect)
in the section of the apache doc to which you referred it shows examples using <VirtualHost> containers which only work in server config context.
based what i have read here these past several years, i would hazard a guess that most WebmasterWorld visitors asking questions in this forum don't have access to their server config file.
The most common situation in which mod_rewrite is the right tool is when the very best solution requires access to the server configuration files, and you don't have that access. Some configuration directives are only available in the server configuration file. So if you are in a hosting situation where you only have .htaccess files to work with, you may need to resort to mod_rewrite.
Optionally, you could simplify it just a touch by removing the domain name. Apache will use the current scheme and hostname.
what if the requested scheme or hostname is non-canonical for the resource?
your suggestion implies multiple redirects before you request the intended resource at the canonical url.
this means more wait time for the user (and this is actual measurable clock time, not "nanotime") and gives the appearance of low technical quality to search engines.
If you can do it in one hop, that's ideal.