Backport to v2.2.x: [http2] delay processing requests upon observing suspicious behavior #3293
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi!
This is a backport of 94fbc54 from #3291 to the v2.2.x branch.
I know that all the tagged releases should be considered deprecated, and that no new version will be released in the future, therefore I don't expect this pull request to be merged. While we are transitioning from
libh2o-evloop
tonghttp2
in DNSdist, we unfortunately need to keep ourh2o
support alive for a little bit longer while the transition is complete, so we have been working on backporting the HTTP2 rapid reset fix on top of 2.2.6, and we decided to share the result in case it helps others.Please note that we unfortunately had to break the ABI to introduce the new timer, so this change will require a rebuild of applications dynamically linked against
libh2o
.Any feedback would be of course appreciated!
Best regards,
Remi Gacogne
PowerDNS.COM BV - https://www.powerdns.com/