Receiving mp_new_connection_id-frame for non-existing uniflow id

[The3ternum]

Upon setting up a connection where my client sets the transport parameter "max_sending_uniflow_id" to 0 it still receives a mp_new_connection_id-frame where the uniflow_id is set to 1, resulting in an error because the client does not have a uniflow with id 1 for the connection.

[qdeconinck]

Indeed, the multipath plugin does not check the value of the transport parameter provided by its peer to reserve new connection ID frames. Going to implement a fix for this :-)

[qdeconinck]

This should have been fixed in the latest commits. Could you check that it is ok now?

[The3ternum]

Running an endpoint on the latest commit seems to indeed solve the issue. Thank you for the fix, closing this issue now.

[mpiraux]

The fix should now be deployed on the public test endpoint as well.