Skip to content

Use resource limits in Kestrel #32033

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

Open
JunTaoLuo opened this issue Apr 21, 2021 · 2 comments
Open

Use resource limits in Kestrel #32033

JunTaoLuo opened this issue Apr 21, 2021 · 2 comments
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-kestrel feature-rate-limit Work related to use of rate limit primitives
Milestone

Comments

@JunTaoLuo
Copy link
Contributor

This is part of the Epic: https://github.com/dotnet/aspnetcore/issues/27464

This issue tracks the adoption of the resource limit APIs in Kestrel which consists of:

@JunTaoLuo JunTaoLuo added enhancement This issue represents an ask for new feature or an enhancement to an existing one area-runtime feature-kestrel feature-rate-limit Work related to use of rate limit primitives labels Apr 21, 2021
@JunTaoLuo JunTaoLuo added this to the 6.0-preview5 milestone Apr 21, 2021
@JunTaoLuo JunTaoLuo modified the milestones: 6.0-preview5, 6.0-preview6 May 19, 2021
@JunTaoLuo JunTaoLuo modified the milestones: 6.0-preview6, Backlog Jul 6, 2021
@ghost
Copy link

ghost commented Jul 6, 2021

We've moved this issue to the Backlog milestone. This means that it is not going to be worked on for the coming release. We will reassess the backlog following the current release and consider this item at that time. To learn more about our issue management process and to have better expectation regarding different types of issues you can read our Triage Process.

@ghost
Copy link

ghost commented Sep 14, 2022

Thanks for contacting us.

We're moving this issue to the .NET 8 Planning milestone for future evaluation / consideration. We would like to keep this around to collect more feedback, which can help us with prioritizing this work. We will re-evaluate this issue, during our next planning meeting(s).
If we later determine, that the issue has no community involvement, or it's very rare and low-impact issue, we will close it - so that the team can focus on more important and high impact issues.
To learn more about what to expect next and how this issue will be handled you can read more about our triage process here.

@amcasey amcasey added area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions and removed area-runtime labels Jun 2, 2023
@amcasey amcasey modified the milestones: .NET 8 Planning, Backlog Feb 14, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-middleware Includes: URL rewrite, redirect, response cache/compression, session, and other general middlewares area-networking Includes servers, yarp, json patch, bedrock, websockets, http client factory, and http abstractions enhancement This issue represents an ask for new feature or an enhancement to an existing one feature-kestrel feature-rate-limit Work related to use of rate limit primitives
Projects
None yet
Development

No branches or pull requests

3 participants