This repository was archived by the owner on Aug 11, 2020. It is now read-only.
quic: client should work when receives invalid preferred address #155
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
If we set
preferredAddressPolicy
toaccept
onQuicClientSession
but receives an invalid preferred address, e.g. we don't define
preferredAddress
on the server, theQuicClientSession
should stillwork. Before this PR, the included test will cause segmetation fault.
the example in
ngtcp2
always return 0 onselect_preferred_address
: https://github.com/ngtcp2/ngtcp2/blob/52d56a90a7766c71c68362dc85f5fdc866760f47/examples/client.cc#L673Checklist
make -j4 test
(UNIX), orvcbuild test
(Windows) passes