BB,
Oh, so many things to correct here!
First, do you know whether you have mod_rewrite, mod_deflate and mod_mime enabled? If so, WHY waste server resources testing these repeatedly? Then, too, MULTIPLE tests of mod_rewrite?
As an engineer, I learned NOT to do a test if you’re not going to do anything with the results. You seem to be testing “just for fun.” Okay, I know that software developers protect themselves from complaints by using wrappers but, as a webmaster, you’re supposed to be smart enough to test once then remove that @#$%.
Second, mod_rewrite will progress through ALL its code making redirections if the conditions are met to do so. Thus, you have conflicting rules which allow redirections long before you get to the WP @#$% (I dislike their code for other reasons but you’re not there yet (their code has superfluous @#$%, too, which makes no sense to me at all - and they used to be better than that until a year or two ago).
On that note, I owe you:
-
RewriteBase can only get you into trouble if you don’t understand that it’s redirecting to a subdirectory. IMHO, simply put your WP code in the directory where WP resides.
-
Unless you’ve modified it, it looks like WP wised up with their index.php RewriteRule (not necessary if canyonvacationrentals’s DirectoryIndex contains index.php).
-
/canyonvacationrentals as a redirection will first attempt to access the root OF THE SERVER before the subdirectory of the DocumentRoot. This is a potential security problem but is certainly unnecessary - especially with the RewriteBase already pointing there.
-
Since canyonvacationrentals is a subdirectory, treat it as such and provide the trailing /.
-
On the security issue, why would you let someone access your security area from jetpack.wordpress.com? Nice backdoor for someone to hack your website!
Regards,
DK