Fix peer updating cid when using an empty cid killing a path
@@ -4963,7 +4963,8 @@ QuicConnRecvPostProcessing(
// sent back out.
//
- if (PeerUpdatedCid || (*Path)->DestCid == NULL) {
+ if ((*Path)->DestCid == NULL ||
+ (PeerUpdatedCid && (*Path)->DestCid->CID.Length != 0)) {
//
// TODO - What if the peer (client) only sends a single CID and
// rebinding happens? Should we support using the same CID over?
