-
Notifications
You must be signed in to change notification settings - Fork 242
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
feat: setup benchmark project for Antiforgery #2033
base: main
Are you sure you want to change the base?
feat: setup benchmark project for Antiforgery #2033
Conversation
Finally! |
|
||
await app.StartAsync(); | ||
|
||
Console.WriteLine("Application started."); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need an endpoint that uses antiforgery. https://learn.microsoft.com/en-us/aspnet/core/security/anti-request-forgery?view=aspnetcore-9.0#antiforgery-with-minimal-apis
As well as a way to get an antiforgery token for the client to use in its requests.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
WRK has ways to fetch a token on the first request and the reuse it for subsequent requests. Check the LUA scripts we have in this repos for auth.
Another option could be to use K6 but I am afraid its perf to be a bottleneck.
sorry for pushes, I am trying to make crank work on perf-machines, and so far only validating if I can confirm that crank run makes expected steps |
Part 1 of ASP.NET Investigate performance of Antiforgery