Add Antiforgery to Middleware order and Built-in middleware sections about aspnetcore.docs HOT 8 OPEN

@guardrex It was opened right from there (see attached screenshots). The Page URL and Content source URL fields contain correct links to the published document and the source code on GitHub. What exactly is wrong?

from aspnetcore.docs.

My bad ...... so much for looking at issues on the phone while OOF! 🙈😆

from aspnetcore.docs.

My bad ...... so much for looking at issues on the phone while OOF! 🙈😆

You guys really need to rest sometimes 😅

from aspnetcore.docs.

I like to try and respond quickly, but it all went horribly wrong this time. I think I thought that this was about the Middleware doc but opened from the Migration article ... even the "M" in both words (links) might have thrown me off 😈. Looking at these on a phone screen isn't a good experience anyway.

The Middleware in Minimal APIs article makes a mention near the end on where to find more information on the Antiforgery Middleware and cross-links to ...

https://learn.microsoft.com/aspnet/core/security/anti-request-forgery?view=aspnetcore-8.0#afwma

... and that's where there's information about placement (ordering). Rick will determine if/where remarks should go when he sees this.

from aspnetcore.docs.

Hello @mmarinchenko ... What are you asking for? The content is already present in the sections.

from aspnetcore.docs.

@guardrex The Antiforgery middleware depends on the order in which it is added to the request processing pipeline (as well as Cors, OutputCaching, RequestTimeouts and several others). This is covered in the migration article in Blazor context, but not in the main middleware documentation.

See Page URL in the description: ASP.NET Core Middleware. The reference links are provided for reference only 🙂

from aspnetcore.docs.

I see ... but the issue has to be opened from the bottom of that article to get the correct metadata and author ping. Re-open the issue from there, and then the author of that article will address it.

from aspnetcore.docs.

@guardrex If you are confused by the Blazor tag, then it was added by @Rick-Anderson, not by me.

from aspnetcore.docs.