Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Calling Request.clone() stops Chrome from being able to read request body #498

Closed
morsdyce opened this issue Mar 2, 2017 · 1 comment
Closed

Comments

@morsdyce
Copy link

morsdyce commented Mar 2, 2017

Hi,

I'm not sure if this is the correct place to post this, If not feel free to close this issue.

I've noticed an issue with Request.clone() implementation in Chrome.
If you clone a request, Chrome network tools are unable to read the request body.
I've set up a test case where you could see this behaviour:
http://glikm.com/fetch.html

I've tested on the following browsers:
Chrome 56.0.2924.87
Firefox 51.0.1
Safari Technology Preview

In Firefox and Safari the request works as normal, but in Chrome the developer tools are missing the Request Payload. I assume this is due to a bug in the implementation of this spec.

@annevk
Copy link
Member

annevk commented Mar 3, 2017

Please file that issue at https://crbug.com/new, thanks!

@annevk annevk closed this as completed Mar 3, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants