Closed vrsinghal closed 1 month ago
@vrsinghal I have had a chance to look at the har file you sent and a few other URLs that produce nextLink options.
The result of https://graph.microsoft.com/beta/$metadata#admin/teams/userConfigurations
does indeed produce a nextLink property that is 7194
characters long.
While URLs can be any length, major browsers are not able to support more than 2000
characters hence why this error is produced.
If you report this issue in the Microsoft Q&A forum, it will get routed to the appropriate team for them to triage and probably see how to reduce the size of the URL generated so that it can be supported on multiple browsers.
Hello @vrsinghal
Thank you for reporting your concern. Unfortunately, we in the Graph Explorer team do not have any ownership of the APIs that are causing you issues. If you report this issue in the Microsoft Q&A forum, it will get routed to the appropriate team for them to triage. https://aka.ms/askgraph This issue will now be closed. If you encounter any issues with Graph Explorer in the future, please feel free to open an issue.
Describe the bug There is an issue with pagination. When we try to follow @odata.nextlink on Graph Explorer we run into:
Expected behavior The request should reach the workload and return correct response.
Screenshots
Additional context This issue is reproducing every time on graph explorer. I am able to see successful response for the same request via postman. HAR logs: https://michev-my.sharepoint.com/:u:/g/personal/vasil_michev_info/EXwD9-LNG7tJs16beWqPzpEBN1cKm0vZoR8IyRZS1gL8Vw?e=Ss1yFh