Skip to content
This repository has been archived by the owner on Sep 29, 2024. It is now read-only.

Can't handle multipart PUSH_REPLY #71

Closed
keeshux opened this issue Mar 22, 2019 · 0 comments
Closed

Can't handle multipart PUSH_REPLY #71

keeshux opened this issue Mar 22, 2019 · 0 comments
Assignees
@keeshux
Labels
bug Something isn't working
Milestone
1.6.2

Comments

@keeshux
Copy link
Member

keeshux commented Mar 22, 2019

Summary

Steps to reproduce

Push a long list of options (commonly route options) so that the server sends PUSH_REPLY in a multipart fashion with push-continuation 2.

What is the current bug behavior?

Throws .malformedPushReply because it can't always find required options like topology, ifconfig etc.

What is the expected correct behavior?

Handle push-continuation correctly (2 = more to come, 1 = last).

Relevant logs and/or screenshots

Possible fixes suggested remediation
@keeshux keeshux added the bug Something isn't working label Mar 22, 2019
@keeshux keeshux self-assigned this Mar 22, 2019
@keeshux keeshux modified the milestones: 1.5.1, 1.5.2 Mar 22, 2019
@keeshux keeshux mentioned this issue Mar 22, 2019
Closed
@keeshux keeshux removed this from the 1.5.2 milestone Apr 1, 2019
@keeshux keeshux added this to the 1.6.2 milestone Apr 16, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@keeshux keeshux

Labels
bug Something isn't working
Projects
None yet
Milestone
1.6.2
Development

No branches or pull requests
1 participant
@keeshux