Redirect adding 1/2 second delay! -- moving from old O365 APIs to Microsoft Graph -
we have existing code uses old office365 api. in api, first step before oauth use discovery api identify appropriate end points api user signing in. different user domains had different end-points (something https://foo.my-sharepoint.com/.... subseqently, api use rest methods against end-point.
now trying move graph api. , find performance worse. root cause seems each api call graph api leads 302 redirect after 1/2 second delay! instead of looking appropriate endpoint, seems happen inefficiently on every single api call.
has else seen this? workarounds? making our system way slower.
some details requested @baywet ...
the original request fetch content of file identified file path (constructed c# sdk): https://graph.microsoft.com/v1.0/me/drive/root:/appsheet//nationalparks.xlsx:/content
"1track-my.sharepoint.com" actual o365 site. old api figure out during initial discoveryapi phase pay cost of lookup once , directly hit appropriate endpoint.
Comments
Post a Comment