🚀 go-pugleaf

A long time ago, I stopped using my Best account for web hosting and
put some Redirect rules in my .bhtaccess files to point at my new
site. I think someone automagically converted .bhtaccess files to
Apache-compliant .htaccess files resulting in subtle breakage. I had a
bunch of rules for:

Redirect /foo.html http://www.example.com/foo.html
Redirect /bar.html http://www.example.com/bar.html

followed by a catchall:

Redirect / http://www.example.com/

Unfortunately, the mod_rewrite rules that replaced my Redirect rules
work differently as written:

RewriteRule ^/foo.html(.*)$ http://www.example.com/foo.html$1 [R]

isn't quite the same, because subsequent rules are tested and applied.
The final rule:

RewriteRule ^(.*)$ http://www.example.com/$1 [R]

isn't right because the prior rules were meant to be [R,L] rules that
short-circuit to the end of mod_rewrite's execution. This way, the
catch-all rule still gets applied, totally munging the request into
something like http://www.example.com/http://www.example.com/foo.html

So pay attention if you were using Redirect-type commands in your
.bhtaccess files. There are some corner cases where the wrong thing
might be happening.
-- 
mikehan+&$#^@best.com