In addition, I’m finding many companies don’t even know that Chrome has begun blocking some types of insecure content already. Even though the blog post was published in October of 2019, I’m still seeing a lot of confusion about the topic when working with clients. Since it’s a common issue, Chrome announced a staged plan in October so site owners would have plenty of time to research and fix mixed content issues on their sites. There are security risks associated with that, so Chrome wants to eliminate that risk in the future (by blocking mixed content from loading). For example, loading an image file over http from an https page. Mixed content is a common issue across sites where secure pages attempt to load insecure content. In October of 2019, Google announced a plan to gradually block mixed content over time.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |