Skip to content
New issue

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

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

Already on GitHub? # to your account

.Net: fix: expected empty response in rest APIs #9999

Merged

Conversation

baywet
Copy link
Member

@baywet baywet commented Dec 17, 2024

fixes #9990

Signed-off-by: Vincent Biret <vibiret@microsoft.com>
@baywet baywet requested a review from a team as a code owner December 17, 2024 13:19
@markwallace-microsoft markwallace-microsoft added the .NET Issue or Pull requests regarding .NET code label Dec 17, 2024
@github-actions github-actions bot changed the title fix: expected empty response in rest APIs .Net: fix: expected empty response in rest APIs Dec 17, 2024
@markwallace-microsoft markwallace-microsoft added this pull request to the merge queue Jan 6, 2025
Merged via the queue into microsoft:main with commit d201b5e Jan 6, 2025
18 checks passed
@baywet baywet deleted the fix/empty-api-response branch January 7, 2025 18:53
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
.NET Issue or Pull requests regarding .NET code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

.Net: 202 response with no content/content-type response header makes the rest API operation runner fail
3 participants