Not All Plugins Too Tertiary Political Party Code Back Upwardly Ssl
Sunday, April 14, 2013
Edit
With Blogger right away providing (optional) HTTPS, on all blogs, we're seeing a few anxious reports inwards Blogger Help Forum: Get Help alongside an Issue.
Not enabling "HTTPS Redirect" won't hateful that every plugin or service volition operate - if your readers pick out to role SSL, to access your blog, unfortunately.
One of the reasons why it is taking Blogger hence long to larn SSL working, is that they accept to let for our blogs, using non Blogger code.
Too many Blogger blogs role non Blogger code that does non back upward SSL.
One of the reasons, why all websites don't accept HTTPS yet, is they accept to aspect for other websites to render it.
Rex Swain does non excogitation to upgrade - ever.
It's like to the game of Pickup Sticks. You can't (shouldn't) upgrade your blog, until your accessories together with plugins back upward SSL.
I role the Rex Swain HTTP (yes "HTTP:"!) trace, for diagnostics, frequently. HTTPS is non a nothing toll upgrade!
Somebody else may depend upon content from your weblog - together with his website can't travel upgraded, because his website displays a Mixed Content alert ("Not secure"), because of his link to your blog. And a 3rd website must wait, for him to upgrade his website.
Your weblog may role a plugin that does non render SSL access.
For plugins that don't back upward SSL, you lot may accept to pick out betwixt having a broken plugin - or dropping role of those services, until they, too, tin upgrade. Or don't forcefulness HTTPS.
Don't enable the "HTTPS Redirect" option, if you lot role plugins inwards your blog, that don't back upward SSL.
Be patient - together with operate on weblog content.
Be patient. Encourage the websites, that you lot depend upon, to enable SSL on their service - together with hence you lot tin produce the same, alongside your blog. And keep publishing your blog.
Encourage Blogger to restore the "HTTPS Availability" option. Make SSL access optional, for each weblog - non forced SSL optional.
With #Blogger having enabled HTTPS on all BlogSpot published blogs, weblog owners are seeing problems caused past times non Google websites that don't offering SSL yet. The "HTTPS Redirect" pick actually should travel "HTTPS Availability", again.
https://productforums.google.com/forum/#!category-topic/blogger/2HV3zzclGCg
https://productforums.google.com/forum/#!category-topic/blogger/9rp4vZhBAhQ
https://productforums.google.com/forum/#!category-topic/blogger/p3DlfKBszTM
https://productforums.google.com/forum/#!category-topic/blogger/QMFbAsOvvdc
I'm getting an error, on i of my plugins.The respond won't travel encouraging.This content is non withal available over encrypted connections.What tin I do?
Don't enable "HTTPS Redirect", on your blog.
Not enabling "HTTPS Redirect" won't hateful that every plugin or service volition operate - if your readers pick out to role SSL, to access your blog, unfortunately.
One of the reasons why it is taking Blogger hence long to larn SSL working, is that they accept to let for our blogs, using non Blogger code.
Too many Blogger blogs role non Blogger code that does non back upward SSL.
One of the reasons, why all websites don't accept HTTPS yet, is they accept to aspect for other websites to render it.
It's like to the game of Pickup Sticks. You can't (shouldn't) upgrade your blog, until your accessories together with plugins back upward SSL.
I role the Rex Swain HTTP (yes "HTTP:"!) trace, for diagnostics, frequently. HTTPS is non a nothing toll upgrade!
Note re HTTPS: I often larn requests to render back upward for HTTPS. But I'm afraid I accept no fiscal incentive to heighten the viewer. Despite thousands of hits a day, well-nigh nobody clicks on ads. So, I accept this asking on my to-do list, simply frankly I doubtfulness I'll always larn to it.
Somebody else may depend upon content from your weblog - together with his website can't travel upgraded, because his website displays a Mixed Content alert ("Not secure"), because of his link to your blog. And a 3rd website must wait, for him to upgrade his website.
Your weblog may role a plugin that does non render SSL access.
For plugins that don't back upward SSL, you lot may accept to pick out betwixt having a broken plugin - or dropping role of those services, until they, too, tin upgrade. Or don't forcefulness HTTPS.
Be patient - together with operate on weblog content.
Be patient. Encourage the websites, that you lot depend upon, to enable SSL on their service - together with hence you lot tin produce the same, alongside your blog. And keep publishing your blog.
Encourage Blogger to restore the "HTTPS Availability" option. Make SSL access optional, for each weblog - non forced SSL optional.
With #Blogger having enabled HTTPS on all BlogSpot published blogs, weblog owners are seeing problems caused past times non Google websites that don't offering SSL yet. The "HTTPS Redirect" pick actually should travel "HTTPS Availability", again.
https://productforums.google.com/forum/#!category-topic/blogger/2HV3zzclGCg
https://productforums.google.com/forum/#!category-topic/blogger/9rp4vZhBAhQ
https://productforums.google.com/forum/#!category-topic/blogger/p3DlfKBszTM
https://productforums.google.com/forum/#!category-topic/blogger/QMFbAsOvvdc