Skip to content

Possibility to not respond on M-SEARCH if the ST doesn't match #6

Description

@EDDragonWolf

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.

image

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?

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions