akka/akka-http

Timeout for connections half-closed by peer

Open

#4,105 opened on 2022年4月12日

GitHub で見る
 (0 comments) (0 reactions) (0 assignees)Scala (1,311 stars) (598 forks)batch import
1 - triagedhelp wantednice-to-have (low-prio)t:coret:server

説明

As observed in #1977, a server connection is allowed to be half-closed by the peer. That means it might stay open indefinitely if the server has the idle-timeout disabled and the server never tries to send something again.

Using a idle-timeout is a working solution to this case.

For busy servers, it might be a problem to keep connections open for the potentially long idle-timeout. For these cases, it might make sense to introduce another timeout that governs how long to keep open a connection on the server if the client has closed its side. This is an optimization for a very particular case, so for now we treat it with low priority.

コントリビューターガイド

技術スタック
scala
領域
backend
Issue 種別
feature
難度新しい貢献者にとっての実装難度です。1 は非常に小さな変更、5 は専門的な作業です。
4
推定時間経験ある貢献者が調査、実装、テスト、pull request 準備にかけるおおよその時間範囲です。
3-5 days
活動状況Issue が今どれだけ取り組みやすいかを示します。新しい、活発、古い、ブロック中、またはメンテナー入力待ちなどです。
stale
明確さ期待される変更、受け入れ条件、次の手順がどれだけ明確かを示します。
clear
前提条件
Akka HTTP basicsUnderstanding of idle timeoutKnowledge of connection lifecycle
初心者向け度初回貢献者にどれだけ取り組みやすいかを 1-100 で推定したスコアです。
35
調査方針
Investigate the current idle timeout implementation in Akka HTTP. Look at the code handling connection state, specifically how half closed connections are managed. Refer to the linked issue #1977 for context. Consider where to add a new timeout configuration for half closed connections and how it would interact with existing idle timeout.