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.