fix(image): unblock fetch from frontend.sprixe.dev to bridge on localhost#223
Merged
privaloops merged 1 commit intomainfrom Apr 27, 2026
Merged
Conversation
…host Chromium 117+ enforces Private Network Access: a page served over HTTPS that fetches an HTTP localhost URL triggers a permission prompt (or a hard block depending on the feature flag state). The kiosk has no pointer to dismiss the prompt, so the bridge probe in the frontend silently failed and launches kept falling back to the embedded TS engine. Two flags added to start-kiosk.sh: - --disable-features=BlockInsecurePrivateNetworkRequests turns the enforcement off entirely. - --unsafely-treat-insecure-origin-as-secure=http://127.0.0.1:7777 belt-and-suspenders: even if the disable-features flag changes name in a future Chromium, this one keeps marking the bridge origin as trusted so the secure-context check passes. Both are safe in this single-tenant kiosk where the only reachable HTTP endpoint on 127.0.0.1 is the bridge we ship ourselves.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This was referenced Apr 27, 2026
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.
Chromium 117+ enforces Private Network Access: a page served over
HTTPS that fetches an HTTP localhost URL triggers a permission prompt
(or a hard block depending on the feature flag state). The kiosk has
no pointer to dismiss the prompt, so the bridge probe in the frontend
silently failed and launches kept falling back to the embedded TS
engine.
Two flags added to start-kiosk.sh:
enforcement off entirely.
belt-and-suspenders: even if the disable-features flag changes name
in a future Chromium, this one keeps marking the bridge origin as
trusted so the secure-context check passes.
Both are safe in this single-tenant kiosk where the only reachable
HTTP endpoint on 127.0.0.1 is the bridge we ship ourselves.