11-01-2014, 09:57 PM
I found a couple of oddities with pilight (at least in v5) ssdp discovery.
The first is just an oddity, I'm using a Python library and the builtin Python httplib as a class for dealing with http header (responses). For some reason it expects white space after the header name colon, e.g.:
Expects:
Freaks out with:
This is a bug imho in the Python httplib library, hence this being an oddity.
That being said the spec http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html states a single space is preffered. And pilight is not adding a space, again not a bug but it would be nice if it did.
The other oddity (and I think this is a bug) is that the pilight daemon does not respond to service requests for ssdp:all nor upnp:rootdevice. I think this is expected per http://www.w3.org/TR/discovery-api/.
None of these are big deals but they do make using some off the shelf tools for ssdp awkward.
The first is just an oddity, I'm using a Python library and the builtin Python httplib as a class for dealing with http header (responses). For some reason it expects white space after the header name colon, e.g.:
Expects:
Code:
location: something
Freaks out with:
Code:
location:something
This is a bug imho in the Python httplib library, hence this being an oddity.
That being said the spec http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html states a single space is preffered. And pilight is not adding a space, again not a bug but it would be nice if it did.
The other oddity (and I think this is a bug) is that the pilight daemon does not respond to service requests for ssdp:all nor upnp:rootdevice. I think this is expected per http://www.w3.org/TR/discovery-api/.
None of these are big deals but they do make using some off the shelf tools for ssdp awkward.