Call Protected APIs from a Blazor Web App

Blog Discussions
, ,
22

I run the code from GitHub successfully and while using Microsoft Edge got this warning message in the browser console. Will this solution still work in future Edge version?

Third-party cookie will be blocked in future Microsoft Edge versions as part of unpartitioned third-party cookie deprecation.

Also has this message:

  1. Migrate entirely to HTTPS to have cookies sent to same-site subresources

Error

  1. A cookie was not sent to an insecure origin from a secure context. Because this cookie would have been sent across schemes on the same site, it was not sent. This behavior enhances the SameSite attribute’s protection of user data from request forgery by network attackers.

Resolve this issue by migrating your site (as defined by the eTLD+1) entirely to HTTPS. It is also recommended to mark the cookie with the Secure attribute if that is not already the case.

  1. AFFECTED RESOURCES
1. 1 cookie

  1. |Name|Domain & Path|

| — | — |
|.AspNetCore.Antiforgery.wqPgKSmMo-Y|localhost/|

2. 1 request

  1. ping?requestUrl=https%3A%2F%2Flocalhost%3A7255%2F&browserName=&userAgent=Mozilla%2F5.0+(Windows+NT+10.0%3B+Win64%3B+x64)+AppleWebKit%2F537.36+(KHTML%2C+like+Gecko)+Chrome%2F126.0.0.0+Safari%2F537.36+Edg%2F126.0.0.0&browserIdKey=window.browserLink.initializationData.browserId&browserId=4cf6-68d7&_=1721757141922
    • Learn more: How Schemeful Same-Site Works