Quote:
Originally Posted by thommy
good luck for your revenues :-)
|
Sometimes switching prematurely can be an issue too. If you're using something like IFRAMEs or other inline content, and the programs haven't yet shifted over to HTTPS, there's going to be even more nasty security warnings. You really need to do (or have already done) an audit of all third party content
before you make the switch to HTTPS, to make sure they can also support it. I assumed everything would be fine but it turned out that what was a clean site via HTTP suddenly had icons and warning dialogs when switched to HTTPS. As mentioned above I had to wait for a couple of programs to provide a fix before my site loaded cleanly again.