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

message parsing robustness #68

Closed
mnot opened this issue May 24, 2018 · 3 comments · Fixed by #247
Closed

message parsing robustness #68

mnot opened this issue May 24, 2018 · 3 comments · Fixed by #247

Comments

@mnot
Copy link
Member

mnot commented May 24, 2018

... is awfully far from the definition of the message format; IME people read the start of section 3 in isolation and don't see the text below. Maybe move 3.5 up?

@royfielding
Copy link
Member

Agreed. I have fixed this in 33c709c

@mnot
Copy link
Member Author

mnot commented Oct 10, 2018

How about moving the three paras starting with "Although the line terminator..." to 2.1, and moving the CRLF out of the definition of request-line and status-line into HTTP-message, to be consistent with header-field? Then all of the text about CRLF is in one place.

@annevk
Copy link
Contributor

annevk commented Oct 15, 2018

See also #62.

@mnot mnot added the editorial label Oct 16, 2018
@mnot mnot self-assigned this Sep 2, 2019
mnot added a commit that referenced this issue Sep 2, 2019
@mnot mnot closed this as completed in #247 Sep 9, 2019
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