A test implementation of a UPnP device. Uses a trimmed down version of 2.1 Device Description from UPnP Device Architecture v1.0 document.

The device provides no services, but a single presentation URL. Once the presentation URL is accessed by a HTTP client, a nice 'Hello' message will be shown.

• GUPnP
• glib

For Python version:

./testdev.py

For vala version:

valac testdev.vala --pkg gupnp-1.0
./testdev

In either case, the log output will contain a line looking like this:

(Vala)
...
** Message: testdev.vala:118: location address: http://192.168.1.136:58000
...

(Python)
...
DEBUG:root:location address http://192.168.1.136:49724
...

Make a curl request to http://<address>/config like this:

user@host:~/code/upnp: curl http://192.168.1.136:58000/config -D -
HTTP/1.1 200 OK
Date: Tue, 07 Apr 2015 20:49:24 GMT
Content-Type: text/plain
Content-Length: 135

Hello!

This is an example response. You might want to redirect the client
to anoter location or implement a nice web page right here.
user@host:~/code/upnp:

A real life use case, when the UPnP advertisement daemon does not handle the presentation. Since the URL included in device.xml is relative, the client will attempt to access it using the Location header found in SSDP messages. An example message broadcast by GUPnP looks like this:

NOTIFY * HTTP/1.1
Host: 239.255.255.250:1900
Cache-Control: max-age=1800
Location: http://192.168.1.136:55016/1a6c9157-162a-4787-b5cf-4b91be2cc454.xml
Server: Linux/3.19.2-1-ARCH UPnP/1.0 GUPnP/0.20.13
NTS: ssdp:alive
NT: upnp:rootdevice
USN: uuid:1a6c9157-162a-4787-b5cf-4b91be2cc454::upnp:rootdevice

When a client performs GET request to http://192.168.1.136:55016/config a redirect to a predefined URL (hardcoded in _handle_config callback - check the code) will be made.