Clever Geek Handbook

Chrome 58 Unsecured Data in URL

A recent update to Chrome 58 caused the issue. When Selenium launches a Chrome instance, it does not navigate to the original url as in Chrome 57. Now that Chrome is launched through Selenium, we get this problem:

ChromeNotSecureData

It just hangs right there and won't move. Has anyone else found a workaround for this?

If I go back to Chrome 57 ... no problem with that! Unfortunately, now we need to use 58.

I have multiple nodes in my mesh and this happens on each one. I thought it was Group Policy or something, but the fact that it works great on 57 doesn't make any sense to me.

** Update: Another issue I'm running into is that it often takes two or three attempts to open the browser before it finally launches.

+3


source to share


1 answer


Add the argument - enable-automation to your webdriver. Chrome 58 requires https by default and it won't render pages that can't handle it, enabling automation lets the browser know the webdriver is in control and render the page safely.



+2


source






More articles:


All Articles