EOFException in RealBufferedSource.readUtf8LineStrict(): 0-bytes in stream #1517

swankjesse · 2015-03-19T21:08:32Z

We're getting an EOF exception with size=0 in the stream.

java.io.EOFException: \n not found: size=0 content=...
            at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:200)
            at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:187)
            at com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:80)
            at com.squareup.okhttp.internal.http.HttpEngine.readNetworkResponse(HttpEngine.java:791)
            at com.squareup.okhttp.internal.http.HttpEngine.access$200(HttpEngine.java:90)

(Forked from issue 1114.)

The text was updated successfully, but these errors were encountered:

simtse · 2015-04-01T17:14:55Z

@swankjesse mentioned the following

My hypothesis is that these are just badly-behaving webservers, or proxy servers or something. In OkHttp 2.3 we're now including more information about the connection when this problem occurs. This happens to normal devices, like your Moto X 2014.

So this is the problem that I am running into and it doesn't seem to be the other issue [https://github.com//issues/1518] related to corruption of data. @swankjesse , if you think it is the webserver, do you know what on the server might trigger this only a 5-10% of the time or maybe even less? Most of the time it works, but once in a while I get this response.

swankjesse · 2015-04-01T19:37:19Z

@simtse what device are you using?

simtse · 2015-04-01T21:13:54Z

We are using Nexus 4, Nexus 5, Samsung Galaxy S4, Galaxy Note 3, OnePlus One, Nexus 9, HTC One M7, HTC One S, HTC One One X, Moto X 2013. Those are the ones we use most often.

iglaweb · 2015-05-02T08:41:50Z

Getting this issue on Huawei P6-U06 4.2.2. The problem seems to appear quite often only while downloading large files e.g. 600 Mb. The only solution is to make a connection retry?(
I'am using a GET request.

aniketalhat · 2015-06-10T02:28:36Z

Hi,

I am facing this issue during low traffic time, I have 24 threads connected to the influxdb server making batch/sec updates. Little insight might help.
Caused by: retrofit.RetrofitError: unexpected end of stream on Connection{:8086, proxy=DIRECT hostAddress= cipherSuite=none protocol=http/1.1} (recycle count=0)
at retrofit.RetrofitError.networkError(RetrofitError.java:27)
at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:395)
at retrofit.RestAdapter$RestHandler.invoke(RestAdapter.java:240)
at org.influxdb.impl.$Proxy5.write(Unknown Source) ~[na:na]
at org.influxdb.impl.InfluxDBImpl.write(InfluxDBImpl.java:126)
at
... 21 common frames omitted
Caused by: java.io.IOException: unexpected end of stream on Connection{:8086, proxy=DIRECT hostAddress=influxdb cipherSuite=none protocol=http/1.1} (recycle count=0)
at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:211)
at com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:80)
at com.squareup.okhttp.internal.http.HttpEngine.readNetworkResponse(HttpEngine.java:917)
at com.squareup.okhttp.internal.http.HttpEngine.access$300(HttpEngine.java:95)
at com.squareup.okhttp.internal.http.HttpEngine$NetworkInterceptorChain.proceed(HttpEngine.java:902)
at com.squareup.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:760)
at com.squareup.okhttp.Call.getResponse(Call.java:274)
at com.squareup.okhttp.Call$ApplicationInterceptorChain.proceed(Call.java:230)
at com.squareup.okhttp.Call.getResponseWithInterceptorChain(Call.java:201
at com.squareup.okhttp.Call.execute(Call.java:81)
at retrofit.client.OkClient.execute(OkClient.java:53)
at retrofit.RestAdapter$RestHandler.invokeRequest(RestAdapter.java:326)
... 25 common frames omitted
Caused by: java.io.EOFException: \n not found: size=0 content=...
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:200)
at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:191)
... 36 common frames omitted

ivamluz · 2015-07-09T17:19:45Z

Hi guys,

Are you aware of any workaround possible? The issue doesn't seem to happen on Android 5.0.2, but happens quite often on 4.1.2 and 4.1.4 (at least).

Thanks,
Ivam

GBouerat · 2015-07-22T13:25:41Z

Same issue here,
IOException is thrown in 3 ms every 10, 20 or 30 requests ...

OkHttpClient client = new OkHttpClient();
client.setRetryOnConnectionFailure(false);
HttpURLConnection connection = new OkUrlFactory(client).open(url);

It never happens with okhttp include in Lollipop.

swankjesse · 2015-07-22T15:29:07Z

Running into this issue? Please send me a test case!

dmoneyUK · 2015-08-20T15:10:13Z

I recreated this issue on OkHttp 2.4.0 in debug. I set a break point on the line "Response response = getResponse().getResponse();" in the HttpURLConnectionImpl# getHeaders() method. My tomcat server is configured connectionTimeout="10000" for SSL connector. So, if I hold the getHeaders() method and let the server to close the connection. The client side always complains:

"org.springframework.web.client.ResourceAccessException: I/O error on POST request for "https://xxx.xxx.xxx.xxx/myapplication/api/myservice": unexpected end of stream on Connection{xxx.xxx.xxx.xxx:443, proxy=DIRECT@ hostAddress=xxx.xxx.xxx.xxx cipherSuite=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA protocol=http/1.1} (recycle count=3); nested exception is java.io.IOException: unexpected end of stream on Connection{xxx.xxx.xxx.xxx:443, proxy=DIRECT@ hostAddress=xxx.xxx.xxx.xxx cipherSuite=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA protocol=http/1.1} (recycle count=3)
...
Caused by: java.io.IOException: unexpected end of stream on Connection{xxx.xxx.xxx.xxx:443, proxy=DIRECT@ hostAddress=xxx.xxx.xxx.xxx cipherSuite=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA protocol=http/1.1} (recycle count=3)
at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:211)
at com.squareup.okhttp.internal.http.HttpTransport.readResponseHeaders(HttpTransport.java:80)
at com.squareup.okhttp.internal.http.HttpEngine.readNetworkResponse(HttpEngine.java:917)
at com.squareup.okhttp.internal.http.HttpEngine.readResponse(HttpEngine.java:793)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.execute(HttpURLConnectionImpl.java:439)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getResponse(HttpURLConnectionImpl.java:384)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getHeaders(HttpURLConnectionImpl.java:150)
at com.squareup.okhttp.internal.huc.HttpURLConnectionImpl.getHeaderFieldKey(HttpURLConnectionImpl.java:202)
at com.squareup.okhttp.internal.huc.DelegatingHttpsURLConnection.getHeaderFieldKey(DelegatingHttpsURLConnection.java:202)
at com.squareup.okhttp.internal.huc.HttpsURLConnectionImpl.getHeaderFieldKey(HttpsURLConnectionImpl.java:25)
at org.springframework.http.client.SimpleClientHttpResponse.getHeaders(SimpleClientHttpResponse.java:92)
... 9 common frames omitted

Caused by: java.io.EOFException: \n not found: size=0 content=...
at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:200)
at com.squareup.okhttp.internal.http.HttpConnection.readResponse(HttpConnection.java:191)
... 27 common frames omitted

I cannot image any reason that would cause the client spend more than 10s to read the response. Any idea?

swankjesse · 2015-08-20T15:14:28Z

@dmoneyUK could you isolate this into a test case? There's lots of examples in CallTest, and MockWebServer is pretty capable around setting up timeouts etc.

sylvia43 · 2015-08-22T22:39:14Z

I'm getting the same problem while creating a Websocket: http://stackoverflow.com/questions/32161398/okhttp-websocket-unexpected-end-of-steam-on-connection

EDIT: Figured it out. The server was closing the connection and not sending any data back, due to a misconfiguration on my part. That said, maybe there could be a way to make that error clearer for the developer?

dmoneyUK · 2015-08-24T07:21:05Z

@anubiann00b In my case, the "Unexpected end of stream" was also caused by server's connection timeout. But the question why does the client spend so much time to read a simple response? My server side timeout is 10 second, and the request was not a file upload/download, it is supposed to complete in 1 second at most. I cannot find any log in server side showing the request is received.

dmoneyUK · 2015-08-24T07:23:59Z

@swankjesse Is there anyway to turn the okhttp log to debug level? In my case, the client spend too much time to read a simple response and server's connection timeout. i did not find any information about what happened there.

swankjesse · 2015-08-25T02:46:35Z

@dmoneyUK I recommend you try out https://charlesproxy.com to inspect your HTTP traffic. We may add trace logging to OkHttp, but we don't have it currently.

dmoneyUK · 2015-09-10T07:47:49Z

Hi, I found 90% of this kind of exceptions happening in my environment are from "GET" request. And I found a code block in httpengine as below:

 private Connection createNextConnection() throws RouteException {
 ConnectionPool pool = client.getConnectionPool();

// Always prefer pooled connections over new connections.
for (Connection pooled; (pooled = pool.get(address)) != null; ) {
  if (networkRequest.method().equals("GET") || Internal.instance.isReadable(pooled)) {
    return pooled;
  }
  closeQuietly(pooled.getSocket());
}
....
}

Can you tell me why the GET request does not need to check connection readable?

swankjesse · 2015-09-10T12:35:20Z

@dmoneyUK OkHttp can silently recover from those GET failures, and it’s more efficient to try and recover vs. test first. (The API to check whether a connection is readable is a bit of a hack!)

GBouerat · 2015-09-22T09:49:32Z

Still present in version 2.5.0 ...

with connection.setRequestProperty("Connection", "close"); there is no more errors, but it's not a valid solution ...

dmoneyUK · 2015-09-29T12:44:13Z

I solved this In my envrionment. In my case, when OkHttp tries to re-use a connection which has been closed by my tomcat server, the exception happens. My solution is to configure the tomcat server's "keepAliveTimeout" > than the client's connection timeout so that the server will never close a connection before the client.

Thanks @JakeWharton

ZeWaren · 2015-09-29T13:58:51Z

If you called setRetryOnConnectionFailure(false); on your connection, you will never have a solution to prevent those i/o errors.

Java's sockets have per design no way of knowing TCP connections are in state CLOSE_WAIT without trying to read from them.

OkHTTP or whatever library you use will send data into the closed connection, try to read from it, (only then) realize that it was closed, open/use another one and send the request again.

Configuring a very long Keep-Alive duration on your servers will prevent most of the errors, but if your clients are behind any kind of proxies, your configuration won't be relevant anymore.
Also, if your servers handle many requests and connection, the ops team that configures your front servers might not like the ideas of having tens thousands of unused opened connections.

jeaking · 2015-10-13T08:27:11Z

@swankjesse Do you think adding isReadable() check for GET request while retryOnConnectionFailure is set to false is good idea?

doridori · 2015-12-03T17:54:14Z

Im getting this on ~1/6 calls using POST

Caused by: java.io.EOFException: \n not found: size=0 content=...

If I do the post via curl all is fine...this on okhttp 2.6.0 on android 6.0

lexius · 2015-12-08T11:12:44Z

The same error here.

 java.io.IOException: unexpected end of stream on Connection{192.168.10.22:443, proxy=DIRECT@ hostAddress=192.168.10.22 cipherSuite=TLS_RSA_WITH_AES_128_CBC_SHA protocol=http/1.1} (recycle count=0)

 Caused by: java.io.EOFException: \n not found: size=0 content=...
                                                                          at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:201)

On okhttp 2.6.0 and android 6.0

laalto · 2015-12-09T14:59:28Z

I get this problem consistently on one particular REST service. PUT and DELETE requests fail with this error while GET on the same service works just fine and other services in the same network environment work with no problems.

The same PUT/DELETE also go through successfully when run through Charles Proxy in SSL proxying mode.

Tracing with Wireshark shows the following, comparing to the trace from the proxied request that works:

Much more TLS application data being sent with less intermediate ACKs (resends?)
Eventually the server RSTs the connection and the 5 outstanding app data packets get RST,ACK

I don't know if it makes a difference but the URL is about 5500 bytes in size - a very long identifier embedded in it. In GET with this service endpoint the URLs are only around 660 bytes i.e. well below what fits in one packet.

Android versions 4.x-6.0, many devices including plain x86_64 6.0 emulator, OkHttp 2.5.0 and 2.6.0.

laalto · 2015-12-09T15:54:01Z

Ok, did an experiment and shortened the requestLine by replacing the 5+kB identifier with a shorter one "foo". The request went through all right and got the expected error message from backend. So maybe it's about the way long request lines are written out i.e. not waiting for ACKs before proceeding, and then a server-side component backs off rapidly. I'll contact the network infra people to see if there's some e.g. DoS prevention in load balancers/proxies here.

stepheaw · 2017-12-05T18:42:58Z

@crossle did you fix the issue?

sschuberth · 2018-01-30T08:51:08Z

The issue can be easily reproduced by trying to download a source artifact from SourceForge, like https://master.dl.sourceforge.net/project/tyrex/tyrex/Tyrex%201.0.1/tyrex-1.0.1-src.tgz. Neither adding .addHeader("Connection", "close") to the request nor adding .retryOnConnectionFailure(true) to the client helps.

Given how big of a site SourceForge is, even if it was a server configuration issue, can we reopen this to track adding a work-around, @swankjesse? Also, I have no issues downloading that file with Firefox or curl.

EDIT: Turns out the problem with downloading from SourceForge can be avoided by upgrading to at least java 8u161.

herusdianto · 2018-02-05T06:07:13Z

Hi, anyone have solution for this problem?

Kolyall · 2018-02-15T13:31:48Z

How to resolve the issue?

java.io.IOException: unexpected end of stream on Connection{develop.by:8000, proxy=DIRECT@ hostAddress=develop.by/195.***.***.**:8000 cipherSuite=none protocol=http/1.1}
    at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:205)
    at okhttp3.internal.http.CallServerInterceptor.intercept(CallServerInterceptor.java:88)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
    at okhttp3.internal.connection.ConnectInterceptor.intercept(ConnectInterceptor.java:45)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
    at okhttp3.internal.cache.CacheInterceptor.intercept(CacheInterceptor.java:93)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
    at okhttp3.internal.http.BridgeInterceptor.intercept(BridgeInterceptor.java:93)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
    at okhttp3.internal.http.RetryAndFollowUpInterceptor.intercept(RetryAndFollowUpInterceptor.java:125)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:147)
    at okhttp3.internal.http.RealInterceptorChain.proceed(RealInterceptorChain.java:121)
    at okhttp3.RealCall.getResponseWithInterceptorChain(RealCall.java:200)
    at okhttp3.RealCall$AsyncCall.execute(RealCall.java:147)
    at okhttp3.internal.NamedRunnable.run(NamedRunnable.java:32)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1113)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:588)
    at java.lang.Thread.run(Thread.java:818)
Caused by: java.io.EOFException: \n not found: limit=0 content=…
    at okio.RealBufferedSource.readUtf8LineStrict(RealBufferedSource.java:227)
    at okhttp3.internal.http1.Http1Codec.readHeaderLine(Http1Codec.java:212)
    at okhttp3.internal.http1.Http1Codec.readResponseHeaders(Http1Codec.java:189)
	... 19 more

Code:

final Request request = new Request.Builder()
              .get()
              .url("http://develop.by:8000")
             .build();

OkHttpClient okHttpClient = new OkHttpClient.Builder()
              .readTimeout(30, TimeUnit.SECONDS)
              .writeTimeout(30, TimeUnit.SECONDS)
              .build();

WebSocket webSocket = okHttpClient.newWebSocket(request, new WebSocketListener() {...}

DavidPerezIngeniero · 2018-03-07T15:09:55Z

Is the last solution good?
Why is this issue closed, if it looks like unsolved?.
I was working before with HttpUrlConnection and never experienced this problem. Server hasn't changed. So, probably the problem is with OkHttp.
Working with Android 4.4.

Server is Jetty based with Java 8.

deberle · 2018-03-09T21:01:09Z

I am having this problem too.
It started to occur since we switched our server to an S3 instance.

rhonyabdullah · 2018-03-14T07:36:30Z

Hello, i'm facing this issue, reading this stackoverflow question says that this error is causing from the server. Any solution ?

GeoffLedak · 2018-03-15T20:39:16Z

I encountered this issue as well and was able to resolve it.

I was working with some existing code which used Retrofit. We have 3 different dev environments, the same endpoint was working fine in 2 of the environments, but I was getting this exception when using the third.

All 3 servers were returning the exact same 200 response.

The code I was working with was passing a boolean value of false as an empty @Body in a PUT call.

I changed this to an empty String instead and now it works fine, though I don't entirely understand why. Something somewhere must be looking for the null terminator character that an empty String provides.

hlogmans · 2018-05-03T07:19:00Z

For posterity: I ran into this error frequently when using the Square bindings for Xamarin, using an NetworkInterceptor. This crash is thrown frequently (as described before) but should be handled by the retry on connection code. But somehow in Xamarin it crashes in such a way the retry is never done, and the exception is propagated to the app.

See mattleibow/square-bindings#20

orende · 2018-05-21T10:26:54Z

I ran into this problem recently when I was sending requests to a web server that was still in the process of starting up (it was being started by a docker container), which seemed to cause the server to send empty headers back to the client. The solution in that case was to wait for the server to be completely up before sending requests.

rasik1010 · 2018-06-28T10:21:48Z

i have same issue and i find some solution:
the problem is HttpLoggingInterceptor , when we use HttpLoggingInterceptor that time the error java.io.EOFException: \n not found: limit=1 content=0d… comes

and when i use bellow code that time error not cumming, but if we dont use HttpLoggingInterceptor then we can not see API call logs in android studio logcat :(

`public static Retrofit getRestAdapter() {
// HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
// interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);

    OkHttpClient.Builder httpClient = new OkHttpClient.Builder();
    httpClient.addInterceptor(new Interceptor() {
        @Override
        public okhttp3.Response intercept(Chain chain) throws IOException {
            Request request = chain.request().newBuilder().addHeader("Connection", "close").build();
            return chain.proceed(request);

        }
    });

    return new Retrofit.Builder()
            .baseUrl(Configuration.getBaseUrl())
            .client(httpClient.build())
            .addConverterFactory(GsonConverterFactory.create())
            .build();

}`

i think if we can set Headers in HttpLoggingInterceptor then error can be solve but i didnt found any ways to set headers in HttpLoggingInterceptor object :(

anybody can help in this case please reply here ... thanks

rhonyabdullah · 2018-07-03T03:51:44Z

Good news,
This issue resolved just by adding Connection header as @rasik1010 say but i'm still using HttpLoggingInterceptor and it's working fine.
addHeader("Connection", "close")

rasik1010 · 2018-07-03T04:59:02Z

@rhonyabdullah where/how did you put addHeader("Connection", "close") in HttpLoggingInterceptor? can you share that code please?

houdangui1985 · 2018-07-05T10:09:27Z

@rasik1010 you are right, only disable the HttpLoggingInterceptor works for me. I tried addHeader("Connection", "close") and disable the Accept-Encoding gzip by updating the Accept-Encoding to "identity" , they both don't work @rhonyabdullah

rhonyabdullah · 2018-07-09T10:39:07Z

Using okHttpVersion = "3.10.0"
I'm using kotlin, but it is still readable i think. I'm writing this answer without any IDE, i'm just using this comment box, sorry if any mistake:

internal fun OkHttpClient.Builder.defaultBuilder(isDebug: Boolean)
        : OkHttpClient.Builder {
    if (isDebug) {
        addInterceptor(HttpLoggingInterceptor().setLevel(HttpLoggingInterceptor.Level.BODY))
    }
    connectTimeout(ApiConstant.TIME_OUT_IN_SECONDS, TimeUnit.SECONDS)
    readTimeout(ApiConstant.TIME_OUT_IN_SECONDS, TimeUnit.SECONDS)
    writeTimeout(ApiConstant.TIME_OUT_IN_SECONDS, TimeUnit.SECONDS)
    return this
}

private fun getRequestHeader(chain: Interceptor.Chain): Request {
   return chain.request().newBuilder()
              .addHeader("Connection", "close")
              ..(my another header params)
              .build()
}

val clientBuilder: OkHttpClient.Builder = OkHttpClient.Builder().defaultBuilder(isDebug)
clientBuilder.addInterceptor { chain -> chain.proceed(getRequestHeader(chain)) }

return Retrofit.Builder()
                .baseUrl(myBaseUrl)
                .addConverterFactory(GsonConverterFactory.create())
                .client(clientBuilder.build())
                .build()

rasik1010 · 2018-07-12T06:25:45Z

hi guys, recently we changed our server and now i am using bellow using HttpLoggingInterceptor and the error java.io.EOFException: \n not found: limit=1 content=0d… gone!!!!!

Now the issue is fixed, error was from server side, changed hosting server and issue was fixed automatically. earlier i was hosting on TSOHost where this issue was arraving
so i think this error its because of server

    public static Retrofit getRestAdapter() {

        HttpLoggingInterceptor interceptor = new HttpLoggingInterceptor();
        interceptor.setLevel(HttpLoggingInterceptor.Level.BODY);

        OkHttpClient.Builder httpClient = new OkHttpClient.Builder();
        httpClient.addInterceptor(interceptor);
       
        return new Retrofit.Builder()
                .baseUrl(Configuration.getBaseUrl())
                .client(httpClient.build())
                .addConverterFactory(GsonConverterFactory.create())
                .build();
    }

wonmo01 · 2018-09-15T01:39:08Z

I faced the same issue Caused by: java.io.EOFException: \n not found: limit=0 content=….

The issue was when requests were made in conjunction with
Connection: keep-alive
Transfer-Encoding: chunked
with a long JSON response in the body, but the body was not written according to Chucked Transfer Encoding spec. https://en.wikipedia.org/wiki/Chunked_transfer_encoding

Like the suggestions above, adding Connection: close resolved the issue since it triggered to use UnknownLengthSource instead of ChunkedSource.

Alternative workaround is reading byte[] from ResponseBody.byteStream(), however this would mean the server response is not following Http1.1 spec where it sends Transfer-Encoding: chunked but the body format is not inserting

<< Size of chunk >>\r\n
<< Chunk body >>\r\n
...
repeat as many times
...
0\r\n
\r\n

OR,

the response header can specify Content-Length header.

ghost · 2019-06-18T08:05:25Z

I faced the same error / stacktrace but with another cause; therefore the described workarounds did not work for me.

My problem was the authentication at the server: In my application, I get URLs in the form http://user:[email protected]. The user information are extracted and sent to the server in the Authorization header. But the credentials have not been removed from the URL, so I the requests contained the credentials both in the headers and in the URL. This caused a server (Spring Boot application) to misbehave, causing the error described in this issue.

Removing the credentials from the URL solved the problem for me

malwinder-s · 2019-08-05T14:22:35Z

          .addHeader("Connection", "close")

Didn't worked.

kwek20 · 2019-12-02T17:03:17Z

For me this happened when i connected to a server with HTTP, but it actually should have used HTTPS, check your URL!

OhhhThatVarun · 2023-06-21T10:03:24Z

@dotgc I have the exact use case. Could you let me know what you did to fix the error in your Android app? I'm also seeing them in our logs.

swankjesse mentioned this issue Mar 19, 2015

EOFException in RealBufferedSource.readUtf8LineStrict #1114

Closed

swankjesse added the bug Bug in existing code label Apr 19, 2015

swankjesse added this to the 2.5 milestone Apr 19, 2015

swankjesse modified the milestones: Icebox, 2.5 Aug 1, 2015

dmoneyUK mentioned this issue Aug 21, 2015

Add test for "unexpected end of stream" excpetion #1813

Closed

yschimke mentioned this issue Feb 5, 2018

okhttp fails with IOException: gzip finished without exhausting source but GZIPInputStream works #3759

Closed

1 task

hlogmans mentioned this issue May 3, 2018

OkHttp3: custom network interceptor crash handling makes interceptor useless mattleibow/square-bindings#20

Open

swankjesse removed this from the Icebox milestone Nov 4, 2018

diemol mentioned this issue Dec 19, 2018

Radom failure when run selenium tests in parallel with error info as 'cannot forward the request unexpected end of stream on Connection` zalando/zalenium#742

Open

UnreachableCode mentioned this issue Jan 17, 2019

Android implementation of HTTPClient throwing up java.io.IOException dotnet/standard#1055

Closed

terrajobst mentioned this issue Jan 24, 2019

Android implementation of HTTPClient throwing up java.io.IOException dotnet/android#2651

Closed

alex3305 mentioned this issue Aug 22, 2019

Failing tests (FORWARDING_TO_NODE_FAILED?) zalando/zalenium#939

Closed

gotev mentioned this issue Feb 24, 2021

Return java.io.EOFException Android 11 gotev/android-upload-service#571

Closed

2 tasks

Grt1228 mentioned this issue May 23, 2023

请求长文本时，返回报错 Grt1228/chatgpt-java#143

Closed

EOFException in RealBufferedSource.readUtf8LineStrict(): 0-bytes in stream #1517

EOFException in RealBufferedSource.readUtf8LineStrict(): 0-bytes in stream #1517

Comments

swankjesse commented Mar 19, 2015

simtse commented Apr 1, 2015

swankjesse commented Apr 1, 2015

simtse commented Apr 1, 2015

iglaweb commented May 2, 2015

aniketalhat commented Jun 10, 2015

ivamluz commented Jul 9, 2015

GBouerat commented Jul 22, 2015

swankjesse commented Jul 22, 2015

dmoneyUK commented Aug 20, 2015

swankjesse commented Aug 20, 2015

sylvia43 commented Aug 22, 2015

dmoneyUK commented Aug 24, 2015

dmoneyUK commented Aug 24, 2015

swankjesse commented Aug 25, 2015

dmoneyUK commented Sep 10, 2015

swankjesse commented Sep 10, 2015

GBouerat commented Sep 22, 2015

dmoneyUK commented Sep 29, 2015

ZeWaren commented Sep 29, 2015

jeaking commented Oct 13, 2015

doridori commented Dec 3, 2015

lexius commented Dec 8, 2015

laalto commented Dec 9, 2015

laalto commented Dec 9, 2015

stepheaw commented Dec 5, 2017

sschuberth commented Jan 30, 2018 • edited Loading

herusdianto commented Feb 5, 2018

Kolyall commented Feb 15, 2018 • edited Loading

DavidPerezIngeniero commented Mar 7, 2018 • edited Loading

deberle commented Mar 9, 2018

rhonyabdullah commented Mar 14, 2018

GeoffLedak commented Mar 15, 2018

hlogmans commented May 3, 2018

orende commented May 21, 2018

rasik1010 commented Jun 28, 2018 • edited Loading

rhonyabdullah commented Jul 3, 2018

rasik1010 commented Jul 3, 2018

houdangui1985 commented Jul 5, 2018

rhonyabdullah commented Jul 9, 2018

rasik1010 commented Jul 12, 2018 • edited by yschimke Loading

wonmo01 commented Sep 15, 2018 • edited Loading

ghost commented Jun 18, 2019

malwinder-s commented Aug 5, 2019

kwek20 commented Dec 2, 2019

OhhhThatVarun commented Jun 21, 2023

sschuberth commented Jan 30, 2018 •

edited

Loading

Kolyall commented Feb 15, 2018 •

edited

Loading

DavidPerezIngeniero commented Mar 7, 2018 •

edited

Loading

rasik1010 commented Jun 28, 2018 •

edited

Loading

rasik1010 commented Jul 12, 2018 •

edited by yschimke

Loading

wonmo01 commented Sep 15, 2018 •

edited

Loading