akka/akka-http

Timeout for connections half-closed by peer

Open

#4,105 opened on Apr 12, 2022

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Scala (598 forks)batch import
1 - triagedhelp wantednice-to-have (low-prio)t:coret:server

Repository metrics

Stars
 (1,311 stars)
PR merge metrics
 (Avg merge 1d 10h) (2 merged PRs in 30d)

Description

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.

Contributor guide

Research direction
Review issue #1977 for context on half closed connections. Study the existing idle timeout configuration and implementation in akka http. Understand TCP half close semantics. Propose a new timeout for half closed connections and implement it in the server logic.
Tech stack
scala
Domain
backend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
ScalaAkkanetworking concepts
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50