[DevTools] Possible regression: when payload of POST is blob, data does not show up in Headers tab
Reported by
kaycebas...@gmail.com,
Apr 3 2017
|
||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3057.0 Safari/537.36 Steps to reproduce the problem: 1. Open http://jsbin.com/lebapeyoxi/1/edit?html,output 2. Open Network panel 3. Click "Click Me" 4. Click "json" to inspect the XHR 5. Go to "Headers" tab in DevTools What is the expected behavior? The body (AKA payload) of the POST request is displayed in the "Request Payload" section of the Headers tab What went wrong? The "Request Payload" section is missing Did this work before? Yes m50 (stable) Chrome version: 59.0.3057.0 Channel: canary OS Version: OS X 10.12.3 Flash Version: Someone from the community reported this issue. I'm just forwarding it along. See https://twitter.com/matt_crute/status/847504060081229825 for a more in-depth discussion
,
Apr 4 2017
Tested this issue on Mac 10.12.4 with chrome #50.0.2624.0 and also in M45 and M55 builds. For the provided url in comment #0, didn't see any "Request Payload" in the headers tab. Attaching the screen-shot for reference. kaycebasques@ could you please look into it and let us know your observations.
,
Apr 6 2017
Yes, although this may be a bit difficult to do because blobs are allowed to have very large amounts of binary data and we currently do not have a good UI to display this. Thanks, I'll put it in the queue.
,
Apr 20 2017
As per comment #4, removing needs-bisect label
,
May 19 2017
This issue is possibly related to https://bugs.chromium.org/p/chromium/issues/detail?id=520538, where we can't inspect sendBeacon() using Blob (which is only required because we need to set the Content-Type).
,
May 22 2017
,
Jun 22 2017
allada@: bump! paul irish wants it fixed, we've got to do something fast!
,
Jul 20 2017
Issue 662970 has been merged into this issue.
,
Jul 20 2017
Issue 650775 has been merged into this issue.
,
Jul 24 2017
Why has 650775 been closed? Does it mean that the current issue is not only about fixing the regression, but also about creating a separate tab for the payload?
,
Jul 24 2017
#11 They are related to each-other on the technical front. The cause of this bug is the fact that the data lives in the browser process if it's a BLOB, but we only receive the POST data from the renderer process just before it is sent off to the browser process and we cannot block while we wait for the data to be obtained from browser. The technical part comes in the fact that we may need to introduce a new protocol method to get this data from browser, however if we do this, it will pose a new UI problem because we'll need to figure out a way to let the user know that we have data but they will need to perform an action to obtain it. This is where you bug comes in. If we do it as a new tab the UI problem is solved. We are also considering having some kind of "RAW" viewer which POST data might be the best fit there.
,
Dec 11 2017
bump - any progress on this?
,
Dec 14 2017
,
Mar 1 2018
This had been fixed some time ago.
,
Mar 1 2018
|
||||||||
►
Sign in to add a comment |
||||||||
Comment 1 by ajha@chromium.org
, Apr 4 2017