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

Legacy support, what is the specification? #36

Open
vinniefalco opened this issue Jun 30, 2017 · 1 comment
Open

Legacy support, what is the specification? #36

vinniefalco opened this issue Jun 30, 2017 · 1 comment

Comments

@vinniefalco
Copy link

The function parse_http_version does not accept versions below HTTP/1.0. However parse_headers allows only LF to mark the end of header:

} else if (*buf == '\012') {

This seems non-conforming to rfc7230, what is the rationale?

@kenballus
Copy link

RFC 7230 allows bare LF as a line ending for headers:

Although the line terminator for the start-line and header fields is
the sequence CRLF, a recipient MAY recognize a single LF as a line
terminator and ignore any preceding CR.

Very similar text appears in RFC 9112. This issue should therefore probably be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants