Justin
06-27-2012, 12:10 AM
After I purchased an SSL Certificate, it's been possible for web users to access all my add-on domains via https://, which is wrong. Typically, when someone purchases an SSL certificate, it only belongs to the website used as the main account, which in my case is mexabet.com. But this is not the case - Google indexed directories like
https://zestle.com/mexabet.biz/
https://zinitech.com/mexabet.biz/
Mexabet.biz is an add-on domain just like zestle.com and zinitech.com. So I don't know why it's possible on a Bluehost server to access an add-on domain via another one by just adding https://. To make matters worse, search engines, including Google, are indexing them.
To block access to those add-on domains with secure connection (https://), I added this code to the .htacces file:
RewriteCond %{SERVER_PORT} ^443$
RewriteRule !^(devzeal.biz|devzeal.com|devzeal.info|devzeal.ne t|devzeal.org|zinitech.biz|zinitech.com|zinitech.i nfo|zinitech.net|zinitech.org|mexabet.biz|mexabet. com|mexabet.info|mexabet.net|mexabet.org|mexabet.u s|mexasoft.com|seotreats.com|zinsolar.biz|zinsolar .com|zinsolar.info|zinsolar.net|zinsolar.org)$ https://www.mexabet.com/emaildirectory/ [R=301,L]
The above Mod_rewrite code only works for the homepages of the add-on domains like https://zestle.com/, but not for their inner pages and folders like https://zestle.com/mexabet.biz/. Even though you can no longer access https://zestle.com/, you can still access https://zestle.com/mexabet.biz/, which I also want to redirect to a desired URL.
I just finished chatting with the Bluehost Support Team, and not surprisingly, I got a generic response that pointed me to a tutorial that doesn't work. I believe that they should have solved the problem for me, because they allow an add-on domain to be accessed through another one by simply adding https:// at the beginning of the URL. I had a similar issue because of purchasing a dedicated IP and that took many chat sessions, trials and errors and more than a week to find a fix.
I'll appreciate if anybody can help me to work out a code that will also block inner directories like https://zestle.com/mexabet.biz/ and not just https://zestle.com/.
https://zestle.com/mexabet.biz/
https://zinitech.com/mexabet.biz/
Mexabet.biz is an add-on domain just like zestle.com and zinitech.com. So I don't know why it's possible on a Bluehost server to access an add-on domain via another one by just adding https://. To make matters worse, search engines, including Google, are indexing them.
To block access to those add-on domains with secure connection (https://), I added this code to the .htacces file:
RewriteCond %{SERVER_PORT} ^443$
RewriteRule !^(devzeal.biz|devzeal.com|devzeal.info|devzeal.ne t|devzeal.org|zinitech.biz|zinitech.com|zinitech.i nfo|zinitech.net|zinitech.org|mexabet.biz|mexabet. com|mexabet.info|mexabet.net|mexabet.org|mexabet.u s|mexasoft.com|seotreats.com|zinsolar.biz|zinsolar .com|zinsolar.info|zinsolar.net|zinsolar.org)$ https://www.mexabet.com/emaildirectory/ [R=301,L]
The above Mod_rewrite code only works for the homepages of the add-on domains like https://zestle.com/, but not for their inner pages and folders like https://zestle.com/mexabet.biz/. Even though you can no longer access https://zestle.com/, you can still access https://zestle.com/mexabet.biz/, which I also want to redirect to a desired URL.
I just finished chatting with the Bluehost Support Team, and not surprisingly, I got a generic response that pointed me to a tutorial that doesn't work. I believe that they should have solved the problem for me, because they allow an add-on domain to be accessed through another one by simply adding https:// at the beginning of the URL. I had a similar issue because of purchasing a dedicated IP and that took many chat sessions, trials and errors and more than a week to find a fix.
I'll appreciate if anybody can help me to work out a code that will also block inner directories like https://zestle.com/mexabet.biz/ and not just https://zestle.com/.