3 ms·
I'll admit up-front that I don't have a solid source that I can cite for this, and there's a good chance that it's outdated by now. That being said: I've heard
by 0xcde4c3db 6y ago
I'll admit up-front that I don't have a solid source that I can cite for this, and there's a good chance that it's outdated by now. That being said:
I've heard several times that this is largely driven by the crappier flavors of "media platform" and bottom-of-the-barrel ad networks breaking in spectacular fashion due to CORS and mixed-content problems when the main site tries to switch to HTTPS.
- munchbunny 6y agoThat was indeed a thing several years ago as ad networks were being forced to support HTTPS, but all of the major ad networks and ad servers have supported HTTPS for years at this point. I don't doubt there are some bespoke ad servers or other dark corners of ad infrastructure where HTTPS support is still lacking, but that should be rare at this point.
- EdwardDiego 6y agoYep, in the industry and if your code or servers triggered mixed content warnings, publishers dropped you fast. That said,we still have to scan every creative for https compliance because a lot of them say they are but aren't.
- OJFord 6y ago> we still have to scan every creative for https compliance What's 'creative' when it's a noun? A producer of 'content'?
- munchbunny 6y agoIt refers to the payload that makes up the ad, e.g. the package of html, JS, CSS, and other assets that the browser actually loads.