search

dotnet / aspnetcore

ASP.NET Core is a cross-platform .NET framework for building modern cloud-based web applications on Windows, Mac, or Linux.
https://asp.net
MIT License
35.48k stars 10.03k forks source link

Limit the speed of Virtual Component #44878

Open Alerinos opened 2 years ago

Alerinos commented 2 years ago

Is there an existing issue for this?

Describe the bug

When using Virtualize, we may encounter a problem when the size of the component is different (the element may go outside the area). Then the components will not function properly and spam occurs in a function call that could trigger a ddos attack.

I believe that it is worth discussing this problem and creating a default limit of e.g. 100ms.

The topic was covered in another issue here: https://github.com/dotnet/aspnetcore/issues/44430#issuecomment-1303574664

Expected Behavior

No response

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

blazor .net 7 rc 2

Anything else?

No response

ghost commented 2 years ago

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.

MackinnonBuck commented 2 years ago

Supporting items with varying height is currently being tracked in https://github.com/dotnet/aspnetcore/issues/25058, so let's use this issue to track throttling the rate at which the browser sends spacer visibility updates to .NET.

ghost commented 1 year ago

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 commented 11 months ago

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.