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

How a HEAD response terminates is version-specific #706

Merged
merged 1 commit into from
Mar 25, 2021

Conversation

martinthomson
Copy link
Contributor

Though I think that this text is correct, an HTTP/3 response only ends when
the stream is closed, not at the end of the header section. I think that it's
not necessary to say this bit anyway.

Though I think that this text is correct, an HTTP/3 response only ends when
the stream is closed, not at the end of the header section.  I think that it's
not necessary to say this bit anyway.
Copy link
Member

@royfielding royfielding left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We need something else here, which you alluded to in a different issue. The client MUST understand that the response will not contain content, since otherwise it looks like the beginning of a GET response.

@royfielding
Copy link
Member

The related parts were done in #700 so this bit can be applied now as editorial.

@royfielding royfielding merged commit 0c243c7 into httpwg:master Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

3 participants