Feature #1005
closedhanging connection instead of rejecting with error status
Description
there so many browser accelerators that tune browser's max connection per site, and user have no knowledge nor aware of the underlying http connection count
so why not just hang connection if there's too much connections from same ip, instead of responding with a error http status code.
we can process $max-concurrent-requests at the same time, while keep $max-concurrent-connections of tcp connections from the same client ip even its request HEAD is parsed, which will be delayed until the 1 of the processing requests is finished.
Updated by gstrauss over 8 years ago
- Related to Feature #641: Add support for graceful load shedding / HTTP 503 added
Updated by gstrauss over 8 years ago
- Description updated (diff)
- Status changed from New to Wontfix
- Assignee deleted (
jan)
Not responding (hanging) some connections is likely to result in terrible user experience, as the request(s) sent on those "hung" connections might be delayed quite a while.
HTTP/2 is aimed at solving this problem for busy sites. (See #2726 for discussion of HTTP/2 in lighttpd, not currently in progress)
With quite a bit of work, mod_evasive might be made to group all connections on the same IP, and then handle one request at a time, iterating across each of the connections from the same IP. However, it would be much easier to limit the number of connections per IP, which mod_evasive can already do.
Updated by gstrauss 11 months ago
- Status changed from Wontfix to Obsolete
- ASK QUESTIONS IN Forums set to No
mod_evasive is no longer part of the lighttpd base
For replacement, see lua mod_evasive
Also available in: Atom