Call Failing in Graph Explorer (works in Postman)

[ghost]

Reported from Brandon Henderson
Head of Digital Valuation & Advisory Strategy

"Below is the GET call I was trying from Graph Explorer that returns the error. I was able to get the same call to work successfully through Postman and then used the Save Response as file method. The item is stored on my desktop which is synced with Onedrive for Business. This failed for both .docx document formats as well as .msg, so it wasn’t an issue specific to the ‘unsupported’ msg file format which I did end up getting to work through Postman too. Screenshots from both Beta and 1.0 endpoints are shown below. Thanks!"

Main “Conversion” landing page: https://developer.microsoft.com/en-us/graph/examples/document-conversion

Resource I was following linked from the above page: https://docs.microsoft.com/en-us/graph/api/driveitem-get-content-format?view=graph-rest-1.0&tabs=http

Example Graph API Call that failed: https://graph.microsoft.com/v1.0/me/drive/items/01XJT27CTESZWUYVYJW5EL7NFWHIRVVTVB/content?format=pdf

AB#9504

[ddyett]

we may need to do something interesting on this one. @bettirosengugi I think we'll need to create an experience that explains to the user that we cannot do the call from a CORS app and area performing a workaround for this, which is to get the path from the items/{id} call then construct the call to the service without headers.