New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 662970 link

Starred by 1 user

Issue metadata

Status: Duplicate
Merged: issue 707852
Owner:
Last visit > 30 days ago
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Request payload

Reported by kamil.ro...@gmail.com, Nov 7 2016

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2840.71 Safari/537.36

Steps to reproduce the problem:
1. var request = new Request("", {method: "post", body: JSON.stringify({test:0})});
fetch(request);//payload visible in network tab (payload1.png)

2. var request = new Request("", {method: "post", body: JSON.stringify({test:0})});
request.clone();
fetch(request);//payload invisible in network tab (payload2.png)

What is the expected behavior?
Payload should be visible after request.clone().

What went wrong?
Payload in network tab in request details is invisible.

Did this work before? No 

Chrome version: 54.0.2840.71  Channel: stable
OS Version: 6.3
Flash Version: Shockwave Flash 23.0 r0
 
payload1.png
46.0 KB View Download
payload2.png
41.6 KB View Download
Cc: tkonch...@chromium.org
Labels: Needs-Feedback
Could you please provide a sample HTML file to reproduce the issue from test team end.

Comment 2 by l...@chromium.org, Nov 14 2016

Owner: allada@chromium.org
You have to just paste the code to the console (e.g. on this webpage):

var request1 = new Request("", {method: "post", body: JSON.stringify({test:0})});
fetch(request1);//request payload visible in network tab

var request2 = new Request("", {method: "post", body: JSON.stringify({test:0})});
request2.clone();
fetch(request2);//request payload invisible in network tab

If I prepare an index.html file it will not work due to "URL scheme must be "http" or "https" for CORS request."
Project Member

Comment 4 by sheriffbot@chromium.org, Dec 2 2016

Labels: -Needs-Feedback Needs-Review
Thank you for providing more feedback. Adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 5 by hdodda@chromium.org, Dec 22 2016

Cc: hdodda@chromium.org
Labels: -Needs-Review M-57
Status: Untriaged (was: Unconfirmed)
Tested on Windows 10 using chrome latest stable M55 #55.0.2883.87 and issue is reproduced.

Issue exists from M54 and M30 to M53 , the behavior is different.

Untriaging the issue , so that it would get addressed.

Thanks!




Comment 6 by hdodda@chromium.org, Dec 22 2016

Labels: OS-Linux OS-Mac

Comment 7 by allada@chromium.org, Jul 20 2017

Mergedinto: 707852
Status: Duplicate (was: Untriaged)
Moving to topic with more discussion.

Sign in to add a comment