grpc / grpc/grpc-web

MS Edge: Getting incomplete data on READY_STATE_CHANGE

Open
#763 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
JavaScript
Stars
9.3k
Forks
802
Avg merge
1d 7h
Merged PRs (30d)
5

Description

Facing a weird issue with Edge, looks like we are getting incomplete responses when they are too long. I was able to track the issue all the way here:

https://github.com/grpc/grpc-web/blob/master/javascript/net/grpc/web/grpcwebclientreadablestream.js#L121

e.g. I have a response that's around 13K long. The length bytes inside the `grpc.web.GrpcWebStreamParser` module indicate that the total response should have a length of `13352`, however the `responseText` length we get in the `READY_STATE_CHANGE` callback is ~4K. This results in the message not being correctly parsed.

Seems that this is only happening in the non-chromium Edge versions <= 18.

Although this seems to be a bug in Edge and not grpc-web itself, I'm posting here to check if anyone else has faced this issue and there's a known fix for this.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.