Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add conn_idle_timeout for server #2355

Open
silence-coding opened this issue Dec 10, 2020 · 2 comments
Open

add conn_idle_timeout for server #2355

silence-coding opened this issue Dec 10, 2020 · 2 comments

Comments

@silence-coding
Copy link
Contributor

Should we add idle timeout for the server? Without idle timeout, the service cannot quickly release idle connections. In this case, the client can set up a large number of idle connections with the hyper server, exhausting the hyper resources.

@CodesInChaos
Copy link

Even if the server implements idle timeouts, an attacker can simply send the data very slowly (slowloris attack).

@silence-coding
Copy link
Contributor Author

silence-coding commented Mar 4, 2021

Although this capability cannot solve slow attacks, when the connection is idle for a long time, it is necessary for the hyper server to close the connection.

Dav1dde added a commit to getsentry/relay that referenced this issue Nov 14, 2024
With the idle time configurable we can prevent a pile up of open
connections which never see any activity.

See also on the hyper issue tracker:
```
hyperium/hyper#3743
hyperium/hyper#1628
hyperium/hyper#2355
hyperium/hyper#2827
```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants