New issue
Advanced search Search tips

Issue 900945 link

Starred by 1 user

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Dev Tools Throws ERR_INVALID_URL When Using 'wss' in V8 Debug URL

Reported by david.s....@gmail.com, Nov 1

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/70.0.3538.77 Safari/537.36

Steps to reproduce the problem:
1. Close all open Chrome windows and start with a new window, without opening Dev Tools.

2. Enter this URL into the address bar:

chrome-devtools://devtools/bundled/js_app.html?experiments=true&v8only=true&wss=hostname:9229/088b3957-ca0b-4694-bc46-e4f73a3369bf

What is the expected behavior?
The expected behavior would be for Dev Tools to display and attempt a connection to the V8 host via wss://.

What went wrong?
Instead of attempting a connection, an error screen is displayed. The error code is ERR_INVALID_URL, screenshot is attached.

Did this work before? N/A 

Chrome version: 70.0.3538.77  Channel: stable
OS Version: 10.0
Flash Version: 

I'm using wss:// to connect via a reverse proxy. 

I found that if you press F12 to open dev tools before trying the above URL then it works as expected -- the debug tools display, Chrome makes a connection via wss:// and everything works fine.

The problem is just the ERR_INVALID_URL when 'wss' is in the query string and dev tools are not already open. This is causing much confusion for my end users, because the problem/solution are not at all clear.
 
screenshot.png
44.6 KB View Download
Labels: Needs-Triage-M70
Cc: swarnasree.mukkala@chromium.org
Labels: Triaged-ET Needs-Feedback
Tried testing the issue on reported chrome version #70.0.3538.77 on Windows 10 by following below steps.

Steps:
=====
1.Launched chrome.
2.Navigated to "chrome-devtools://devtools/bundled/js_app.html?experiments=true&v8only=true&wss=hostname:9229/088b3957-ca0b-4694-bc46-e4f73a3369bf".
3.Observed  "This site can’t be reached" error.
4.Opened devtools using F12 and navigated to same URL, observed that a message as "Debugging connection closed: Websockect disconnected".

Attached screencast for reference.
@reporter: Could you please review attached screencast and confirm if this is the issue you are pointing to.
Thanks.!
900945.mp4
3.3 MB View Download
Yes, the screencast shows the problem I'm referring to.
Project Member

Comment 4 by sheriffbot@chromium.org, Nov 2

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Owner: alph@chromium.org
Labels: Target-72 M-72 FoundIn-71 FoundIn-70 FoundIn-72 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on reported chrome version #70.0.3538.77 and latest canary 72.0.3608.0 using Windows 10, Ubuntu 17.10 and Mac OS 10.14 by following steps as per comment#0 and comment#3.

The behaviour is seen from old M-60builds (#60.0.3112.113). This is a non-regression issue, hence marking it as untriaged and requesting some one from dev team to look into the issue.
Thanks.!
Status: Assigned (was: Untriaged)

Sign in to add a comment