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

close connection item lost its definition #678

Closed
royfielding opened this issue Jan 15, 2021 · 1 comment · Fixed by #813
Closed

close connection item lost its definition #678

royfielding opened this issue Jan 15, 2021 · 1 comment · Fixed by #813

Comments

@royfielding
Copy link
Member

The close connection item used to be defined in Connection as

   The "close" connection option is defined for a sender to signal that
   this connection will be closed after completion of the response.  For
   example,

     Connection: close

   in either the request or the response header fields indicates that
   the sender is going to close the connection after the current
   request/response is complete (Section 6.6).

whereas now its effect is described in Messaging without definition.

I think it should be defined somewhere.

@mnot
Copy link
Member

mnot commented Mar 4, 2021

Messaging 9.3 gets pretty close to that text:

The "close" connection option is used to signal that a connection will not persist after the current request/response.

... with text below that elaborates. What do you want to see here?

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.

2 participants