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

[KNOWN ISSUE] Keep-alive implementation should be different #142

Open
leske42 opened this issue Jan 20, 2025 · 0 comments
Open

[KNOWN ISSUE] Keep-alive implementation should be different #142

leske42 opened this issue Jan 20, 2025 · 0 comments

Comments

@leske42
Copy link
Collaborator

leske42 commented Jan 20, 2025

According to RFC 7230 6.5 and 9112 9.5

Servers will usually have some timeout value beyond which they will no longer maintain an inactive connection.

This means timeout should be reset after activity like a request from client, but now we have it absolute from the beginning.
Nginx apparently has 3 different setting for timeout: keepalive_requests for maximum number of requests processed before closing the connection (this is 1k by default), keepalive_time for maximum time one connection is sustained (this is 1h, for us currently 60 seconds), and keepalive_timeout for periods of inactivity (75 seconds).

@leske42 leske42 changed the title Keep-alive implementation should be different [KNOWN ISSUE] Keep-alive implementation should be different Jan 20, 2025
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

1 participant