Skip to content

BUG: Not handaling correctly if the header termination is \n\n and not \r\n\r\n #62

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
Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

BUG: Not handaling correctly if the header termination is \n\n and not \r\n\r\n #62

wants to merge 1 commit into from

Conversation

fuxpavel
Copy link 

From RFC2616 section 19.3 Tolerant Applications: The line terminator for
message-header fields is the sequence CRLF. However, we recommend that
applications, when parsing such headers, recognize a single LF as a line
terminator and ignore the leading CR.

@pavel-magen
BUG: Not handaling correctly if the header termination is \n\n and no…
fa55292 
…t \r\n\r\n

    From RFC2616 section 19.3 Tolerant Applications: The line terminator for
    message-header fields is the sequence CRLF. However, we recommend that
    applications, when parsing such headers, recognize a single LF as a line
    terminator and ignore the leading CR.
@benoitc benoitc added this to the 0.9.1 milestone Apr 17, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
to investigate working on it
Projects
None yet
Milestone
0.9.1
Development

Successfully merging this pull request may close these issues.
3 participants
@fuxpavel @benoitc @pavel-magen