akka/akka-http

Timeout for connections half-closed by peer

Open

#4,105 建立於 2022年4月12日

在 GitHub 查看
 (0 留言) (0 反應) (0 負責人)Scala (1,311 star) (598 fork)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
議題類型
feature
難度面向新貢獻者的預計實作難度，1 表示很小改動，5 表示專家級工作。
4
預計時間有經驗貢獻者完成調查、實作、測試並準備 pull request 的粗略時間範圍。
3-5 days
活動狀態議題目前的可參與程度：新鮮、活躍、陳舊、阻塞或等待維護者輸入。
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.