Forum Discussion
Sudden CORS errors fetching https://rdweb.wvd.microsoft.com/api/feeddiscovery/webfeeddiscovery.aspx
We've built a solution (web part) that allows users to launch Windows Virtual Desktop apps and desktops from within SharePoint. For this, we used some of the ideas that were described in following ar...
With the help of a colleague I was able to fix the issue myself. Apparently something changed on the service end that now requires an extra header:
With the addition of this header the request is now again successful:
'X-MS-User-Agent': 'com.microsoft.rdc.html/1.0.21.9'
... and the result is a working web part (or widget, to be more precise)!
aaaaand it's broken again...
Same CORS errors, even with the custom header added.
I checked the headers in the regular webclient (at https://rdweb.wvd.microsoft.com/arm/webclient/index.html) and noticed they updated the X-MS-User-Agent header to include a different (newer?) version:
'X-MS-User-Agent': 'com.microsoft.rdc.html/1.0.21.16'instead of'X-MS-User-Agent': 'com.microsoft.rdc.html/1.0.21.9'I updated the header in my code but this didn't fix it.Please help! This doesn't seem to be the right way to integrate with WVD. But what is, then?MarkMarksPoint Did you find a solution? Same situation here...
