fix(stepup): add --remote-allow-origins=* to Behat chrome container - #97
Closed
kayjoosten wants to merge 1 commit into
Closed
fix(stepup): add --remote-allow-origins=* to Behat chrome container#97kayjoosten wants to merge 1 commit into
kayjoosten wants to merge 1 commit into
Conversation
Chrome/Chromium hardened the DevTools (CDP) WebSocket origin check: it now rejects connections with a missing/null Origin header unless started with --remote-allow-origins. A newer lscr.io/linuxserver/chromium:latest build crossed that change, so every @functional Behat scenario in the Stepup repos began failing at the first browser step with: Connection timeout: Empty read; connection dead? (WebSocket\TimeoutException) Adding the flag restores the CDP connection for dmore/chrome-mink-driver while staying on the latest image.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Every
@functionalBehat scenario across the Stepup repos (Gateway, RA, SelfService, …) started failing at the first browser step:Cause
The
chromeservice trackslscr.io/linuxserver/chromium:latest. A newer Chromium build tightened the DevTools (CDP) WebSocket origin check — it now rejects connections with a missing/nullOriginheader unless the browser is started with--remote-allow-origins. Thedmore/chrome-mink-driverWebSocket client sends noOriginheader, so its CDP connection is now refused.Driver versions are unchanged (
dmore/chrome-mink-driver 2.9.3,phrity/websocket 1.7.3) — only the browser image moved.Fix
Add
--remote-allow-origins=*toCHROME_CLI. Safe for a disposable CI/dev browser and keeps the container on the latest image.