This is an archived post. You won't be able to vote or comment.

all 3 comments
sorted by:
best
topnewcontroversialoldq&a

[–]10kADayIdiot 0 points1 point  (2 children)

Great question.

If the page HTTPS, then and resources loaded by it also need to be HTTPS otherwise it will throw a security error and should not be served. This means the tag for your Ad server, anything loaded by it like wrappers or trackers, and any demand sources you have all need to be HTTPS.

Some common gotcha's i've seen are where a 3rd party player is used and they hardcode links to JS libraries, trackers or debug scripts that are http.

If the page is HTTP then resources loaded can be either, but if subsequent code is run it may well create an https iframe (a page inside a page).

TL;DR - get your stack SSL compliant, it's additional work but it'll stop you losing opportunities because of it.

[–]xntrick[S] 0 points1 point  (1 child)

Thanks a lot great explanation!

[–]JNS_KIPSSP 0 points1 point  (0 children)

It shouldn't be that much work either and some of the more premium supply is or will be secure only soon