Quote:
Originally Posted by rowan
Everything's going peachy as I set up my Let's Encrypt certificate, set up Apache on port 443, and start progressively changing references...
Then I discover that one of the affiliate programs I use only supports HTTP. 
It's inlined content (IFRAME) so there's really no option but to accept that it's going result in a broken padlock on most browsers.
Anyone else had the same problem when switching to HTTPS? |
A month later, and it's apparent that inlining a program's HTTP content on my HTTPS site is a serious problem.
Daily referrals to the webcam affiliate program dropped from 90-100, down to around 10. The drop happened immediately after I switched to HTTPS.
This is a massive decrease in leads, and potentially, my long term income from that program.
I'm going to have to set up some kind of HTTP->HTTPS proxy so that I can serve the content myself, because the program is too damn lazy/apathetic to spend a couple of hundred bucks on a certificate and set up HTTPS.
So think twice about switching to HTTPS "because Google told you to"
