New issue
Advanced search Search tips

Issue 819838 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Closed: Sep 19
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug-Regression



Sign in to add a comment

"check Host header for being IP or localhost when connecting over RDP" change causes the WS endpoint to not work with Docker link

Reported by sso...@convoy.com, Mar 7 2018

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.186 Safari/537.36

Steps to reproduce the problem:
1. Run Chromium headless in a Docker container, e.g. https://hub.docker.com/r/alpeware/chrome-headless-trunk/
2. Link to that container from another using the name headless_chrome.
3. Query for the WebSocket endpoint at http://headless_chrome:9222/json/version

What is the expected behavior?
Works

What went wrong?
Fails with an http 500: Host header is specified and is not an IP address or localhost.

Did this work before? Yes The one before https://chromium-review.googlesource.com/c/chromium/src/+/952522

Chrome version:   Channel: n/a
OS Version: 
Flash Version:
 
Labels: Needs-Triage-M64
Components: Internals>Headless
Labels: Proj-Headless

Comment 3 by caseq@chromium.org, Mar 11 2018

Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
This was a security measure. Could you install ssh tunnel so that localhost was connecting to chrome instead?
Status: WontFix (was: Assigned)

Sign in to add a comment