Immutable solution version
Chrome 111 is not compatible with default HTTP Client
Complete solution
If ChromeDriver fails to start after the Chrome 111 update, add --remote-allow-origins=* to your ChromeOptions as a workaround. The underlying issue (Selenium's Java HTTP client setting the Origin header) was fixed in Selenium 4.9.0, so upgrade past that and drop the workaround.
Chrome 111 is not compatible with default HTTP Client
If ChromeDriver fails to start after the Chrome 111 update, add --remote-allow-origins=* to your ChromeOptions as a workaround. The underlying issue (Selenium's Java HTTP client setting the Origin header) was fixed in Selenium 4.9.0, so upgrade past that and drop the workaround.
Context from the issue
gh:SeleniumHQ/selenium#11750: Issue SeleniumHQ/selenium#11750 (closed, 60 comments): ### What happened?
After the Chrome 111 update, you can no longer kick off a chromedriver instance unless you add an additional chrome option:
"--remote-allow-origins=*"
I submitted a bug with Google and they responded, and indicated this has to do with Selenium setting the origin header:
https://bugs.chromium.org/p/chromium/issues/detail?id=1422444
How can we reproduce the issue?
Just update to chrome 111, and try and run a UI selenium test.
I am using Java and Junit. See the link to the Chrome ticket for more details on how I was personally starting the...Evidence
Issue gh:SeleniumHQ/selenium#11750: the reporter asked: Issue SeleniumHQ/selenium#11750 (closed, 60 comments): ### What happened?
After the Chrome 111 update, you can no longer kick off a chromedriver instance unless you add an additional chrome option:
"--remote-allow-origins=*"
I submitted a bug with Google and they responded, and indicated this has to do with Selenium setting the origin header:
https://bugs.chromium.org/p/chromium/issues/detail?id=1422444
How can we reproduce the issue?
Just update to chrome 111, and try and run a UI selenium test.
I am using Java and Junit. See the link to the Chrome ticket for more details on how I was personally starting the... The verified answer was: If ChromeDriver fails to start after the Chrome 111 update, add --remote-allow-origins=* to your ChromeOptions as a workaround. The underlying issue (Selenium's Java HTTP client setting the Origin header) was fixed in Selenium 4.9.0, so upgrade past that and drop the workaround. Evidence thread: https://github.com/SeleniumHQ/selenium/issues/11750By @issueatlas · Version 1 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_dK0oPaEZRu3C-92YK5Wt2g" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Chrome 111 is not compatible with default HTTP Client <span>— Vectle</span></a>