Quote:
Originally Posted by JOKER
Hi Thommy,
You're talking iframes and frames here... (Unsecured Content / Mixed Content Warnings)
Simply linking to http:// from a https:// site does not trigger any warnings, AFAIK.
What ManicaMoney are referring to are the new warnings that are displayed on sites that gather user data such as logins if they are on a non-secure protocol.
And I have to agree that if MM wants to have all their sites that have forms SSL enabled the smartest thing to do would be 301 redirects that change the protocol from http to https but leave the link intact as it was.
They can keep pages that do not gather user-data (pages without forms on them like galleries for example) on http if they wanted to without any issues as well.
Just my  worth
//Edit: I think this is what this is about  |
heyyyy I did not hear from you a long time - how is everything?
and SURE you are right as soon as we talk about a regular link (i explained it also wrong-so my fault)- but the "links" they talk about are infact scripts - means they have to get information about browser, geo and stuff like that. so usually they do not link just to a target but letting a script do the job.
in example an ad server would not know wich ad to place if there would not be a script on the page what collects all this data.
in that case it can be done with // in the start because the browser would automatically connect either to the https or the http version, depend what that site is where the script appears.
hope i did it correct now :-)