What is the best way to create an HTTPS mirror for a resource on the Google Blogger platform?

Question

Google Blogger

Good day!
The next question is, there is a domain zone mydomain.ru, in which www.mydomain.ru is a personal domain for a blog on the Google Blogger platform (blogspot.com). Those. www.mydomain.ru is actually a CNAME to ghs.l.google.com. The trouble is that one of the IP ghs.l.google.com - 173.194.71.121 recently got into the register of banned sites, due to another resource located on the same IP. In this connection, the idea arose to make a "mirror" of a resource with HTTPS on a different IP. The problem is complicated by the fact that the resource itself is located on the Google Blogger platform (hosting, a dedicated IP and an SSL certificate are not a problem to order). For myself, I found several ways to solve this problem, but maybe the community will offer something more interesting.
1. Using CloudFlare. They have SSL on their free plan, as well as a detailed FAQ on how to use CloudFlare to access a custom domain on Google Blogger. But I don't like this option, because. I don't want to change NS-servers in the mydomain.ru zone to CloudFlare's ones.
2. The second option to which I came is more interesting. We make a subdomain ssl.mydomain.ru on which we install an SSL certificate and some kind of PHP Proxy, for example, Glype or similar. As a result, when entering ssl.mydomain.ru, the visitor sees the content located on www.mydomain.ru, i.e. blog directly.
Ideally, I would probably really like some kind of solution with a subdomain that will be a mirror of the main resource. I really hope that I explained it clearly;) In this connection, I would like to listen to the recommendations of the community, how would you organize the above? Can you recommend some kind of php-proxy script for these purposes, in addition to Glype or other options for solving the problem?

Answer 1

Officially recommend CloudFlare , ie. your first choice. But in general it is easier to change the platform.
PS

The trouble is that one of the IP ghs.l.google.com - 173.194.71.121 was recently included in the register of banned sites

So that's why most blogs on this platform do not open for me.