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

Overly aggressive slowloris check? #74

Closed
DemiMarie opened this issue Jun 1, 2022 · 1 comment
Closed

Overly aggressive slowloris check? #74

DemiMarie opened this issue Jun 1, 2022 · 1 comment

Comments

@DemiMarie
Copy link

The slowloris check seems to be overly agressive: if I am reading the code correctly, it requires that the entire header arrive by the end of the second call to the parser. The need for this seems to be due to the code not keeping enough state internally.

@DemiMarie
Copy link
Author

Nevermind, I got the return values mixed up. For anyone else reading this: the slowloris check ensures parsing the header (a non-incremental operation) is done no more than twice, avoiding what would otherwise be an O(n²) complexity.

@DemiMarie DemiMarie closed this as not planned Won't fix, can't repro, duplicate, stale Jun 1, 2022
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