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

Semantics: full-duplex related semantics ... #741

Closed
wenbozhu opened this issue Feb 6, 2021 · 2 comments · Fixed by #765
Closed

Semantics: full-duplex related semantics ... #741

wenbozhu opened this issue Feb 6, 2021 · 2 comments · Fixed by #765

Comments

@wenbozhu
Copy link

wenbozhu commented Feb 6, 2021

7.5 briefly touches this topic.

Responses (both final and interim) can be sent at any time after a request is received, even if it is not yet complete

More explicit descriptions are helpful, such as:

  1. responses can be sent at any time, successful for failed ones
  2. responses may be completed before requests are completed. This is described for 100-continue but should not be limited to 100-continue.
  3. for 2), should a client that sees a failure response continues sending the remaining request content?
@wenbozhu
Copy link
Author

wenbozhu commented Feb 6, 2021

  1. is somewhat addressed in http/1.1 messaging when the server also closes the connection

@mnot
Copy link
Member

mnot commented Feb 10, 2021

For (1) and (2), we could adjust to say

All responses, regardless of status code (including non-final responses), can be sent (and complete) at any time...

(3) is situational. We could say something like 'A client that receives a response to its request while that request is still being sent SHOULD continue sending the request, unless some other signal indicates otherwise.' (with appropriate references, perhaps).

@mnot mnot self-assigned this Feb 10, 2021
mnot added a commit that referenced this issue Feb 11, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants