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.

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

ServerSentEventDecoder stops decoding after receiving an illegal field #269

Closed
NiteshKant opened this issue Nov 4, 2014 · 0 comments
Closed

ServerSentEventDecoder stops decoding after receiving an illegal field #269

NiteshKant opened this issue Nov 4, 2014 · 0 comments
Assignees
@NiteshKant
Labels
bug
Milestone
0.3.18

Comments

@NiteshKant
Copy link
Member

On receiving an unexpected field name, the decoder does not set the currentFieldType which results in a NullPointerException (here) when it tries to decode the field value in the next iteration.
@NiteshKant NiteshKant self-assigned this Nov 4, 2014
@NiteshKant NiteshKant added this to the 0.3.18 milestone Nov 4, 2014
@NiteshKant NiteshKant added the bug label Nov 5, 2014
NiteshKant pushed a commit to NiteshKant/RxNetty that referenced this issue Nov 5, 2014
Fixes for 0.3.18
53d285d 
ReactiveX#269(`ServerSentEventDecoder` stops decoding after receiving an illegal field): Now ignoring all data till an EOL after receiving an unidentified field, in essence ignoring that event.
ReactiveX#270: HttpClient should only do relative redirects
ReactiveX#271: URI fragment must be inherited by the redirect location
ReactiveX#272(Guaranteeing sequential notifications from operators/Subjects): Using `SerializedSubject` in `ObservableConnection.getInput()` and `SerializedObserver` in `UnicastContentSubject`
ReactiveX#257 Support relative HTTP redirects
@NiteshKant NiteshKant mentioned this issue Nov 5, 2014
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@NiteshKant NiteshKant

Labels
bug
Projects
None yet
Milestone
0.3.18
Development

No branches or pull requests
1 participant
@NiteshKant