The Wayback Machine - https://web.archive.org/web/20230314055719/https://github.com/dotnet/aspnetcore/issues/47183
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.

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

IIS HTTP/2 headers only response with END_STREAM flag on headers #47183

Open
1 task done
JamesNK opened this issue Mar 14, 2023 · 0 comments
Open
1 task done

IIS HTTP/2 headers only response with END_STREAM flag on headers #47183

JamesNK opened this issue Mar 14, 2023 · 0 comments
Labels
area-runtime Includes: Azure, Caching, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions untriaged

Comments

@JamesNK
Copy link
Member

JamesNK commented Mar 14, 2023

Is there an existing issue for this?

  • I have searched the existing issues

Describe the bug

A gRPC user is hosting their web app with IIS. They have noticed that a headers-only gRPC response (over HTTP/2) sends a HEADERS frame and an empty DATA frame with the END_STREAM flag. This goes against the gRPC HTTP/2 spec, which says the HEADERS frame should have the DATA frame.

Expected Behavior

IIS sends a HEADERS-only response with the END_STREAM flag in the HEADERS frame.

Note that this Kestrel has the correct behavior.

Steps To Reproduce

No response

Exceptions (if any)

No response

.NET Version

No response

Anything else?

No response

@JamesNK JamesNK added the area-runtime Includes: Azure, Caching, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions label Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area-runtime Includes: Azure, Caching, Middleware, Websockets, Kestrel, IIS, ANCM, HttpAbstractions untriaged
1 participant