NET 7 RC2, this functionality is now available when using the Microsoft Identity Platform via the built-in msal.js integration. NET 7 RC1 we introduced support for making dynamic authentication requests with custom parameters in Blazor WebAssembly apps. We also prefixed most builder methods with SetXxxxx to make it obvious these methods will update an existing property of the builder: options.AddBasePolicy(b => b.SetVaryByQuery("*").SetLocking(true)) Dynamic authentication requests with msal.js Some changes were made to the API to make its usage simpler and more consistent.įor example, you can now create an OutputCachePolicyBuilder instance that doesn’t contain the default policy, so you can specify your own logic. Options.AddBasePolicy(builder => builder.SetVaryByHost(false)) For this purpose, we introduced a new SetVaryByHost option: (options => A few users reported the need for cached entries to be shared across domain names. Option to not vary by hostīy default, cached entries are unique per HTTP domain name. In this version, output caching stores the content of the cached entries in a binary format. NET 7 RC2 based on preview feedback from users. See also the full list of breaking changes in ASP.NET Core for.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |