[core,peer] fix multitransport request checks
If the client does not announced support for UDPFECR then do not send a multitransport request and just skip the state.
This commit is contained in:
parent
37936f5cbb
commit
1c8f762721
@ -949,7 +949,8 @@ static state_run_t peer_recv_callback_internal(rdpTransport* transport, wStream*
|
|||||||
break;
|
break;
|
||||||
|
|
||||||
case CONNECTION_STATE_MULTITRANSPORT_BOOTSTRAPPING_REQUEST:
|
case CONNECTION_STATE_MULTITRANSPORT_BOOTSTRAPPING_REQUEST:
|
||||||
if (settings->SupportMultitransport)
|
if (settings->SupportMultitransport &&
|
||||||
|
((settings->MultitransportFlags & INITIATE_REQUEST_PROTOCOL_UDPFECR) != 0))
|
||||||
{
|
{
|
||||||
/* only UDP reliable for now, nobody does lossy UDP (MS-RDPUDP only) these days */
|
/* only UDP reliable for now, nobody does lossy UDP (MS-RDPUDP only) these days */
|
||||||
ret = multitransport_server_request(rdp->multitransport,
|
ret = multitransport_server_request(rdp->multitransport,
|
||||||
|
Loading…
Reference in New Issue
Block a user