: Insecure content warning on ssl page with unsubmitted http form On the secure https section of a website, I just found out that I had an insecure content warning that was killing the "lock"
On the secure https section of a website, I just found out that I had an insecure content warning that was killing the "lock" functionality and hurting conversions (because users didn't have the green lock and were being turned away by that).
The content warning was on a form that was for a google search via http. In other words, a search box that was not being submitted now causes the content warning message on secure pages in google chrome 37!
This was killing conversions for me, and I'd love to be able to pin down when this change was introduced to the wild. Does anyone know anything about that change, or have a way to figure out when the change would have been introduced?
More posts by @Alves908
Terms of Use Create Support ticket Your support tickets Stock Market News! © vmapp.org2024 All Rights reserved.