Open karsten-klein opened 6 months ago
I have the same issue for the last two days
Idem for me. I've a Response status code does not indicate success: 302 (V2 deprecation | redirect) from the Private/Get-CVRFID.ps1 function when invoke-RestMethod is called. I had a script that forced the use of the v2.0 API version. I just switched to v3.0 and it worked.
The issue seems to be fixed. Requests to the former URL are now propagated to the v3.0 URL.
I solved this problem by changing the API version. You can use this link: https://api.msrc.microsoft.com/cvrf/v3.0/updates
When introducing the v3 api it seems that some change causes https://api.msrc.microsoft.com/cvrf/v2.0/updates into circular redirects.