[Bug] HttpTimeout does not work for SSE connection

[hehua2008]

I have configured HttpClient with

            install(HttpTimeout) {
                connectTimeoutMillis = 60_000
                requestTimeoutMillis = 60_000
                socketTimeoutMillis = 180_000
            }

but it does not work for SSE connection.

I checked the source code and found:

public val HttpTimeout: ClientPlugin<HttpTimeoutConfig> = createClientPlugin(
    "HttpTimeout",
    ::HttpTimeoutConfig
) {
    // ...
    on(Send) { request ->
        val isWebSocket = request.url.protocol.isWebsocket()
        if (isWebSocket ||
            request.body is ClientUpgradeContent ||
            request.body is SSEClientContent
        ) {
            return@on proceed(request)
        }

        var configuration = request.getCapabilityOrNull(HttpTimeoutCapability)
        if (configuration == null && hasNotNullTimeouts()) {
            configuration = HttpTimeoutConfig()
            request.setCapability(HttpTimeoutCapability, configuration)
        }
    // ...
}

I have no idea why Ktor skip setting HttpTimeoutConfig for SEE connection ???

I need a long timeout to get SSE response from LLM AI cloud service. A default timeout value of 10 seconds of OkHttpClient used in Ktor is too small for LLM AI cloud service. Some LLM AI cloud service may take more than 10 seconds to generate next response.

So, is this a bug and should be fixed ?
Or will there be a more reasonable solution ?

[marychatte]

We don't set HttpTimeout for SSE requests at all. It's a bug only for the OkHttp engine, I will take a look at it

[marychatte]

@hehua2008 The issue will be fixed here: #4687

[hehua2008]

@hehua2008 The issue will be fixed here: #4687

Thank you very much！😆