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

"15.5.9. 408 Request Timeout" mentions connections #579

Closed
reschke opened this issue Dec 8, 2020 · 3 comments
Closed

"15.5.9. 408 Request Timeout" mentions connections #579

reschke opened this issue Dec 8, 2020 · 3 comments
Assignees
@reschke
Labels
editorial has-proposal semantics

Comments

@reschke
Copy link
Contributor

reschke commented Dec 8, 2020

"If the client has an outstanding request in transit, the client MAY repeat that request on a new connection."
@royfielding
Copy link
Member

I don't think this needs to be changed (connection is a defined term), but if you can think of some other way to say that the 408 implies partial receipt of the last request (which means the connection gone broke) then go ahead.

@mnot
Copy link
Member

mnot commented Dec 9, 2020

Suggestion:

If the client has an outstanding request in transit, the client MAY repeat that request. If the current connection is not usable (e.g., as it would be in HTTP/1.1, because request delimitation is lost), a new connection will be used.

@royfielding
Copy link
Member

+1

@reschke reschke self-assigned this Dec 10, 2020
royfielding added a commit that referenced this issue Dec 11, 2020
@royfielding
Merge pull request #600 from httpwg/reschke-579
9cb779e 
Rephrase prose about connection re-use (fixes #579)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@reschke reschke

Labels
editorial has-proposal semantics
Milestone
No milestone
Development

No branches or pull requests
3 participants
@mnot @reschke @royfielding