A modern programming language that makes developers happier.

kotlinlang

Hi,

we are using ktor-client-apache to fetch some json:

```client.request(url) {
    HttpMethod.Get
    accept(ContentType.Application.Json)
    contentType(ContentType.Application.Json)
    timeout { requestTimeoutMillis = 60 * 1000
              connectTimeoutMillis = 5 * 1000
              socketTimeoutMillis = 60 * 1000 }
}```
Using ktor 2.0.3 we never had any problems, with version 2.1.0 and 2.1.1 sometimes the call fails with:

```org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 41,606; received: 26,090)```
Same code with the old ktor version started to work again correctly.
Anyone having the same problem? Any hint on how to fix it?
Thanks!

Could you please tell me to what endpoint a request should be made to reproduce `ConnectionClosedException` ?

Hi <@U017TSBJ2C9> unfortunately it’s a private endpoint. I’ll try with some other public api to see if I can reproduce it. Will let you know. Thanks!

I'm facing the same issue with current Ktor 2.3.8 with apache client.

```org.apache.http.ConnectionClosedException: Premature end of Content-Length delimited message body (expected: 12 689 932; received:
 8 388 160)
        at org.apache.http.impl.nio.codecs.LengthDelimitedDecoder.read(LengthDelimitedDecoder.java:89)
        at io.ktor.client.engine.apache.ApacheResponseConsumer$consumeContent$1.invoke(ApacheResponseConsumer.kt:54)
        at io.ktor.client.engine.apache.ApacheResponseConsumer$consumeContent$1.invoke(ApacheResponseConsumer.kt:53)
        at io.ktor.utils.io.ByteBufferChannel.writeAvailable(ByteBufferChannel.kt:1472)
        at io.ktor.utils.io.ByteWriteChannel$DefaultImpls.writeAvailable$default(ByteWriteChannel.kt:76)
        at io.ktor.client.engine.apache.ApacheResponseConsumer.consumeContent(ApacheResponseConsumer.kt:53)
        at org.apache.http.impl.nio.client.MainClientExec.consumeContent(MainClientExec.java:329)
        at org.apache.http.impl.nio.client.DefaultClientExchangeHandlerImpl.consumeContent(DefaultClientExchangeHandlerImpl.java:1
5```

It works ok for smaller responses but fails on one api call with larger response. The "recevied" sizes are different every time.

Could this be caused by some network problem?

We resolved the problem by switching the client from Apache to OkHttp
```private val client = HttpClient(OkHttp)```
Don't know what was causing the problem though...

What is the max limit of response Http client can return?

response pay load size when we request from any API?

Ktor doesn't impose constraints on the response payload size.