We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Our server has certain requests giving 204 No Content as a response to a fetch request.
On Chrome, the response object in response.js has a body that is ReadableStream (it is empty though) and bodyUsed = true.
On Microsoft Edge, the response object in response.js has a body = null and bodyUsed = false.
In the source code of response.js if mode === fetch then it expects a body, but this is not the case in Microsoft Edge.
Can you please add a "if response.body === null" style guard on the fetch response logic?
The text was updated successfully, but these errors were encountered:
We are hitting the same issue.
var reader = response.body.getReader()
runs into an error on Edge because the reponse has no body.
Sorry, something went wrong.
I submitted a PR that fixes the issue: #110
No branches or pull requests
Our server has certain requests giving 204 No Content as a response to a fetch request.
On Chrome, the response object in response.js has a body that is ReadableStream (it is empty though) and bodyUsed = true.
On Microsoft Edge, the response object in response.js has a body = null and bodyUsed = false.
In the source code of response.js if mode === fetch then it expects a body, but this is not the case in Microsoft Edge.
Can you please add a "if response.body === null" style guard on the fetch response logic?
The text was updated successfully, but these errors were encountered: