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

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

Open
baywet opened this issue Dec 16, 2024 · 0 comments · May be fixed by #9999
Open

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

baywet opened this issue Dec 16, 2024 · 0 comments · May be fixed by #9999
Labels
.NET Issue or Pull requests regarding .NET code

Comments

@baywet
Copy link
Member

baywet commented Dec 16, 2024

semantic-kernel/dotnet/src/Functions/Functions.OpenApi/RestApiOperationRunner.cs

Line 317 in 62a50f3

var mediaType = contentType?.MediaType ?? throw new KernelException("No media type available.");

I think the guard at line 305 should be expanded to also include 201/202 when the content type response header is absent.

Happy to submit a patch for this!
@markwallace-microsoft markwallace-microsoft added .NET Issue or Pull requests regarding .NET code triage labels Dec 16, 2024
@github-actions github-actions bot changed the title 202 response with no content/content-type response header makes the rest API operation runner fail .Net: 202 response with no content/content-type response header makes the rest API operation runner fail Dec 16, 2024
@baywet baywet linked a pull request Dec 17, 2024 that will close this issue
Open
@sphenry sphenry removed the triage label Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
.NET Issue or Pull requests regarding .NET code
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

.Net: fix: expected empty response in rest APIs baywet/semantic-kernel
3 participants
@sphenry @baywet @markwallace-microsoft