- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Closed
Listed in 2 issues
Copy link
Labels
C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.K-hyper-utilCrate: hyper-utilCrate: hyper-util
Metadata
Metadata
Assignees
Labels
C-featureCategory: feature. This is adding a new feature.Category: feature. This is adding a new feature.E-easyEffort: easy. A task that would be a great starting point for a new contributor.Effort: easy. A task that would be a great starting point for a new contributor.K-hyper-utilCrate: hyper-utilCrate: hyper-util
Activity
max_pending_accept_reset_streams
hyperium/hyper-util#78dsgallups commentedon Dec 28, 2023
It appears that the referenced PR's changes didn't make the cut into 1.0.0. Is there any reason why the pattern of calling the
inner
value on the builder's internal builder should not also occur formax_pending_accept_reset_streams
? If it should, then this parameter should be readded tohyper/src/proto/h2/server.rs
.I'm no git wizard, but I could copy/paste those changes into a new PR for
hyper 1.x
feat(http2): add `max_pending_accept_reset_streams(num)` back to HTTP…
axum 0.7
cduvray/jwt-authorizer#449 remaining items