-
Notifications
You must be signed in to change notification settings - Fork 255
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
Events dropped in streams with mixed CRLF and LF line terminators. #326
Comments
Maybe they should be unified? |
My first thought was that the code on the server I'm testing against should be fixed, but it does conform to the specification. These server-sent events are processed as expected by the EventSource implemented on browsers, and one should expect this implementation to process them as well. This behavior is actually a secondary issue caused by a parsing bug in the eventsource code where each incoming packet is parsed repeatedly from the beginning, rather from the current offset. I should be able to submit a PR soon. |
Is this project totally dead or what?? |
Try |
v2.0.2.
The server sent events spec states that lines must be terminated by LF, CR, or CRLF.
In the case where the field is terminated by a CRLF and the data and dispatch lines use a single LF, no events are emitted.
The text was updated successfully, but these errors were encountered: