- September 1, 2008
- 21,577
- 8,224
- Home Country
-
New Zealand
I'm not sure why you're asking me! ![Big Grin :D :D](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf
http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf
Read section "1.2.2 Device available - NOTIFY with ssdp:alive". It explicitly describes each header.
The way I read the specs:
The problem is that this particular device seems to claim to be UPnP 1.1 compliant ("SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00"). Therefore it should at least be providing the bootid and configid headers.
That UPnP stack version number seems weird to me though. It's as if the device is trying to claim partial UPnP 1.1 compliance.
[edit: I suggest that the person check for software/firmware updates for the device. Maybe they will make it compliant.
]
I suggest you check the UPnP specs:are those 3 headers mandatory in all cases?
http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.0.pdf
http://upnp.org/specs/arch/UPnP-arch-DeviceArchitecture-v1.1.pdf
Read section "1.2.2 Device available - NOTIFY with ssdp:alive". It explicitly describes each header.
The way I read the specs:
- none of the 3 headers are defined for UPnP 1.0
- bootid.upnp.org and configid.upnp.org are required/mandatory for UPnP 1.1
- searchport.upnp.org is optional for UPnP 1.1
The problem is that this particular device seems to claim to be UPnP 1.1 compliant ("SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00"). Therefore it should at least be providing the bootid and configid headers.
That UPnP stack version number seems weird to me though. It's as if the device is trying to claim partial UPnP 1.1 compliance.
In my opinion the library should be as standard-compliant as possible. Based on my interpretation of the standards (I'm not very familiar with them, so I could easily be wrong!) the library should not allow those headers to be null. It would cause difficulty in properly detecting and notifying about configuration changes and device reboots.Could we allow them to be null to detect more devices?
[edit: I suggest that the person check for software/firmware updates for the device. Maybe they will make it compliant.