chrome://inspect: support backends which use chunked transfer encoding for json/* api
Reported by
francisc...@gmail.com,
Jun 8 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_13_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.181 Safari/537.36 Steps to reproduce the problem: 1. Have a backend that responds to the /json/* API for remote debugging 2. Use Transfer-Encoding: chunked 3. Chrome inspector doesn't find any remote instances even though the data is being produced What is the expected behavior? Expected the available instances to be listed in chrome://inspect remote targets but none is displayed. What went wrong? The remote target in chrome://inspect doesn't list instances which respond to the /json/* API with a Transfer-Encoding: chunked (no Content-Length header). If the backend doesn't use Transfer-Encoding, the remote targets are listed correctly. Did this work before? N/A Chrome version: 66.0.3359.181 Channel: n/a OS Version: OS X 10.13.4 Flash Version:
,
Jun 11 2018
,
Jun 11 2018
Thanks for filing an issue! This is not a priority for us, but contributions are always welcome.
,
Dec 4
We are now relying upon Target domain for page discovery. This is unlikely to get addressed. |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jun 11 2018