Google Chrome document.write and https

[wishlist]

Hi

I like to ask about warning messages that appear on google chrome recently.

It never happened before, it just appear recently.

the message is

A Parser-blocking, cross site (i.e. different eTLD+1) script, https://openx.vendercom.com/delivery/fl.js, is invoked via document.write. This MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.

 

A Parser-blocking, cross site (i.e. different eTLD+1) script, https://openx.vendercom.com/delivery/ajs.php?zoneid=121&, is invoked via document.write. This MAY be blocked by the browser in this or a future page load due to poor network connectivity. If blocked in this page load, it will be confirmed in a subsequent console message.See https://www.chromestatus.com/feature/5718547946799104 for more details.

because of this message, google chrome voids our https cert and flag it as "Not Secure".

do you have solution about this?

it appears that google chrome block/ not recommend using document.write.

Everything is working fine (expect this error message and https cert), which means the ads still showing.

we use :

Revive Adserver 3.2.4

Google chrome Version 57.0.2987.133 (64-bit)

I'm looking forward to hear from you

Thanks

[andrewatfornax]

Hi @wishlist,

Is this on a mobile device - hence the discussion about Chrome potentially stopping this working on a 2G connection?

[wishlist]

unfortunatly I'm testing using google chrome on PC.

it only produces error if we use JS method to embed the ads

if we use php method, google chrome doesn't shows any error.

[andrewatfornax]

Hi @wishlist,

Did you managed to get anywhere with this? I don't have a PC, but everything works okay for me with Chrome on my Mac.

[geverwills]

On 4/6/2017 at 7:04 AM, wishlist said:

A Parser-blocking, cross site (i.e. different eTLD+1) script, https://openx.vendercom.com/delivery/fl.js,

According to Google Developers article, you can:

• Use asynchronous script loading, using <script src="..." async> or element.appendChild(),

It is better don't use document.write for CDN, here is workaround:

var script = document.createElement('script');  
script.src = "....";  
document.head.appendChild(script);