Fetch API request body invisible after Request.clone()
Reported by
alvin...@gmail.com,
Sep 25 2017
|
|||||
Issue description
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36
Steps to reproduce the problem:
1. create a Request obj `var r = new Request('/test/', {method:'POST', body: JSON.stringify({a:1})});`
2. clone it `var r2 = r.clone()`
3. fetch it `fetch(r)` or `fetch(r2)`
example:
https://codepen.io/anon/pen/qPqLZV
What is the expected behavior?
I can see the request body in Network->Headers panel.
What went wrong?
I can't see any Request Payload in Network-> Headers panel.
Did this work before? N/A
Chrome version: 61.0.3163.100 Channel: stable
OS Version: OS X 10.12.6
Flash Version:
,
Sep 26 2017
alvingin@ Thanks for the issue. Tested this issue on Windows 7 and Mac OS 10.12.6 using the latest Chrome Stable 61.0.3163.100 and latest Canary 63.0.3223.8 with the steps as below. 1. Launched Chrome and opened the above given link. 2. Opened Devtools and clicked on Network tab. 3. reloaded the page and clicked on the files. 4. Clicked on the headers tab and can observe the request body. Attached is the screen cast for the reference. Can you please confirm if the steps followed in the screen cast is correct. If not, requesting you to please attach the screen cast of the steps followed for the better understanding of the issue. Thanks..
,
Sep 26 2017
thank you for your reply. after you click reload, the code in JS panel has been reverted in the video. you can try this link https://codepen.io/anon/pen/PJWrRO, I have remove the annotation. ps. the server has received the body.
,
Sep 26 2017
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Sep 27 2017
alvingin@ - Thanks a lot for clarification...!! Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #61.0.3163.100 and latest canary #63.0.3223.8. This is a non-regression issue as it is observed from M50 old builds. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Oct 2 2017
|
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ligim...@chromium.org
, Sep 25 2017