UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Start Chrome with `--headless --remote-debugging-port=9222`
2. Connect to `ws://localhost:9222/devtools/browser`

What is the expected behavior?
A connection is established to the browser target.

What went wrong?
HTTP 404

Did this work before? Yes 61.0.3163.49

Chrome version: 62.0.3178.0  Channel: stable
OS Version: Debian GNU/Linux 9
Flash Version: 

This is not a bug, this is a change about how the browser target is used. With version 62 the proper URL is printed on stderr, e.g.:

    DevTools listening on ws://127.0.0.1:9222/devtools/browser/8189fe12-47c3-4b00-a321-e6d8577f3e0b

I know that I can use this URL to manage the targets (`Target` domain), I also know that I can use any other page target to do that, but it just doesn't feel right to use an auxiliary tab for this purpose. Also, one may want to create a new tab when there a re no other tab opened.

So the question is twofold, 1. what's the rationale behind this choice? 2. how can I obtain the proper URL programmatically? (Of course parsing stderr is not an option.)

Thanks.