ckcr4lyf / kiryuu

A highly performant HTTP bittorrent tracker (WIP)
Do What The F*ck You Want To Public License
13 stars 3 forks source link

Support for reporting clients causing HTTP 408 (Timeout) #42

Open ckcr4lyf opened 1 year ago

ckcr4lyf commented 1 year ago

Seems a lot of clients will timeout, before sending anything.

I.e. after completing TCP handshake, they will sit idle, hogging resources, and kiryuu will send HTTP 408 after 5000ms (for now).

image

We can decrease this timeout to something like 1000ms? Earlier thought of 100ms , but it is easily possible the RTT is > 100ms, e.g. here it is ~300ms:

image

Additionally, we can add a post-request hook in actix, where it will report HTTP 408 to some external service (TBD where). Could be compilation option. These may be malicious and can be firewalled off to save resources.