Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Issue with endpoints that return streams or lead to file downloads #903

Closed
zemuldo opened this issue Mar 24, 2021 · 1 comment · Fixed by #1032
Closed

Issue with endpoints that return streams or lead to file downloads #903

zemuldo opened this issue Mar 24, 2021 · 1 comment · Fixed by #1032
Assignees
@millicentachieng
Labels
priority:p1 High priority but not blocking. Causes major but not critical loss of functionality SLA <=7days. type:bug Something isn't working type:content-text Placing appropriate words
Milestone
Aug-2021

Comments

@zemuldo
Copy link

zemuldo commented Mar 24, 2021 •
edited by azure-boards bot
Loading

Describe the bug
When you call endpoints that return streams or endpoints that lead to a file download, Graph Explorer exits with some error.

To Reproduce
Steps to reproduce the behavior:

  1. Go to https://aka.ms/ge
  2. Click run GET https://graph.microsoft.com/v1.0/reports/getYammerGroupsActivityDetail(period='D7')
  3. Graph Explorer returns 400 with empty object
  4. See error

Expected behavior
This should work if the feature of calling piped endpoints is supported.

Screenshots
Here is the request on Graph Explorer
ge-fail-downloads
And same request on postman
yammer-reports-postman

Desktop (please complete the following information):

  • OS: [Windows 10]
  • Browser [Edge]
  • Version [89.0.774.57]

Additional context
Add any other context about the problem here.

AB#8717
@ghost ghost added the ToTriage label Mar 24, 2021
@thewahome thewahome added the CORS label Mar 29, 2021
@adhiambovivian adhiambovivian added type:bug Something isn't working priority:p1 High priority but not blocking. Causes major but not critical loss of functionality SLA <=7days. and removed Bug – P1 labels Jun 29, 2021
@adhiambovivian adhiambovivian added this to the Aug-2021 milestone Aug 10, 2021
@millicentachieng millicentachieng linked a pull request Sep 10, 2021 that will close this issue
CORS workaround to enable downloading of content #1032
Merged
@zemuldo
Copy link
Author

zemuldo commented Oct 1, 2021

Similar issue here https://stackoverflow.com/questions/69377524/not-getting-response-in-ms-graph-reports-api-using-graph-explorer

@adhiambovivian adhiambovivian added type:content-text Placing appropriate words and removed CORS labels May 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@millicentachieng millicentachieng

Labels
priority:p1 High priority but not blocking. Causes major but not critical loss of functionality SLA <=7days. type:bug Something isn't working type:content-text Placing appropriate words
Projects
None yet
Milestone
Aug-2021
Development

Successfully merging a pull request may close this issue.

CORS workaround to enable downloading of content microsoftgraph/microsoft-graph-explorer-v4
5 participants
@adhiambovivian @zemuldo @ddyett @millicentachieng @thewahome