You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
the ssdp_search sets the MX value to 10, allowing the device to have upto 10 seconds to respond. Yet, the RESPONSE_TIMEOUT is set to 5 seconds. The wait loop may exit too early.
socket descriptors and wait time should be reset on every select() call
In ssdp_msearch response, the LOCATION header field is case_insensitive, thus checking against LOCATION may not work all the time (depends on the DIAL server impl). See the spec here where it states
....header fields appearing .... Field names are not case sensitive.
the ssdp_search sets the
MX
value to10
, allowing the device to have upto10
seconds to respond. Yet, theRESPONSE_TIMEOUT
is set to 5 seconds. The wait loop may exit too early.socket descriptors and wait time should be reset on every select() call
In
ssdp_msearch
response, theLOCATION
header field is case_insensitive, thus checking againstLOCATION
may not work all the time (depends on the DIAL server impl). See the spec here where it statesPlease see PR 34
The text was updated successfully, but these errors were encountered: