This prevents people from enabling authorization globally in a meaningful way for Blazor applications, since while you can apply [Authorize] globally through _Imports.Razor, that prevents you poking holes to allow individual access to unauthenticated pages.

The fixes can be:

• Check for [AllowAnonymous] attribute [here](https://github.com/dotnet/aspnetcore/blob/master/src/Components/Authoriz

Create an include (something like https://github.com/dotnet/AspNetCore.Docs/blob/master/aspnetcore/includes/reservedRouting.md

With the info from https://github.com/dotnet/aspnetcore/wiki/MVC-Reserved-Keywords on routing. Be stronger, something like

These keywords should not be used for link generations, as model bound parameters, or top level properties.

Add the include to the 3

Whenever I submit a GET request to the api/public/groups endpoint, the "collections" field for each group returns "None" on every group, even if they have access to collections. I can verify that the

Problem description

I saw comment about nulls caching dotnetcore/EasyCaching#43 (comment), but we have important case when it is necessary.

We develop a low code platform, where our clients can set up some handlers for processing some requests from there websites.

1. Each handler is entity in database, that is cached in memory.
2. Some handlers cou

Beyonce said it best. If you like it then you shoulda put a test on it. Scenarios I like:

• Cert is created with right DN
• Cert is stored to X509Store after creation
• Cert request is not resubmitted
• Handles failures gracefully
• HTTP challenge/response works as expected
• Certificate renewal when cert is about to expiration