Latest version doesn't connect to the server properly [4.1.0] about okhttp-eventsource

[tanderson-ld]

We don't intend to behave a certain way based on externally added interceptors, but perhaps it was leading to modification of the data our code was receiving? I haven't had a change to dig in deeper yet on how peek could interfere. It doesn't seem like it should.

[tanderson-ld]

Hi @rubenquadros12 , thank you for reporting this issue. We have filed it internally as 205140. I'm not sure when one of our engineers will get a chance to investigate, but we'll update this issue when we do. Thank you.

[hiteshchopra11]

Hey @tanderson-ld, thanks for responding. We have identified what caused the issue. Actually it was related to one of the interceptors used by the Okhttp client inside our app. Very similar to this issue, we noticed that one of the interceptors added in the Okhttp client, uses response.peekBody(Long.MAX_VALUE) , which does the following :

Peeks up to byteCount bytes from the response body and returns them as a new response body. If fewer than byteCount bytes are in the response body, the full response body is returned. If more than byteCount bytes are in the response body, the returned value will be truncated to byteCount bytes.

After removing this interceptor from the okhttp client, the connection is successful. Is this an intended behaviour of the library?

[henryngcw]

@hiteshchopra11 Would be very appreciated if you would kindly guide me on how to remove okhttp client interceptor?