Hi,
I'm investigating your SSDP module and trying to use it to implement a custom SSDP discoverable device, but I found one thing that I cannot resolve. If I understood the UPnP specification correctly if the device (service) type doesn't match the ST header value provided in the M-SEARCH request the device/server shouldn't respond.

The source: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf
But I didn't find any way how to not respond with Oat++. If I skip return or return nullptr the program simply crashes.
Of course, I can create an empty response without providing SSDP headers, but it will look like spam for the UDP sockets that listen to the SSDP port.
Is there a way to properly handle it without creating unnecessary responses?
Hi,
I'm investigating your SSDP module and trying to use it to implement a custom SSDP discoverable device, but I found one thing that I cannot resolve. If I understood the UPnP specification correctly if the device (service) type doesn't match the ST header value provided in the M-SEARCH request the device/server shouldn't respond.
The source: http://www.upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0-20080424.pdf
But I didn't find any way how to not respond with Oat++. If I skip
returnorreturn nullptrthe program simply crashes.Of course, I can create an empty response without providing SSDP headers, but it will look like spam for the UDP sockets that listen to the SSDP port.
Is there a way to properly handle it without creating unnecessary responses?