MiniDLNA does not support RegisterDevice SOAP action

[Gareth Halfacree]

MiniDLNA fails to support older UPnP streaming devices which use the RegisterDevice SOAP action. The result is a failure of the device to register itself, and therefore to connect to the MiniDLNA server.

Bug tested on Ubuntu 13.04 AMD64, both with the latest in-repository release and 1.1.0 direct from SourceForge.

To reproduce, connect a Netgear MP101 Music Streamer to a network with a MiniDLNA server, choose the MiniDLNA server from the server list which appears on the MP101 screen at start-up. After a few seconds, "Unable to connect to server" will appear along with the following entry in MiniDLNA's debug log:

[2013/09/27 09:45:40] minidlna.c:1301: debug: HTTP connection from 192.168.0.103:1064
[2013/09/27 09:45:40] upnphttp.c:833: debug: HTTP REQUEST: POST /ctl/X_MS_MediaReceiverRegistrar HTTP/1.1
Host: 192.168.0.11
CONTENT-LENGTH: 10396
Content-Type: text/xml;charset="utf-8"
SOAPACTION: "urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1#RegisterDevice"
<s:Envelope s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/" xmlns:s="http://schemas.xmlsoap.org/soap/envelope/">
<s:Body>
<u:RegisterDevice xmlns:u="urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1">
<RegistrationReqMsg>AgFNUDEwMQAJW9Ftc5OjIxtjAAAddTxjOkNlcnRpZmljYXRlQ29sbGVjdGlvbiB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnIyIgeG1sbnM6Yz0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9EUk0vMjAwNC8wMi9jZXJ0IiBjOlZlcnNpb249IjIuMCI+PGM6Q2VydGlmaWNhdGU+PGM6RGF0YSB4bWxucz0iaHR0cDovL3d3dy53My5vcmcvMjAwMC8wOS94bWxkc2lnIyIgeG1sbnM6Yz0iaHR0cDovL3NjaGVtYXMubWljcm9zb2Z0LmNvbS9EUk0vMjAwNC8wMi9jZXJ0Ij48YzpQdWJsaWNLZXk+PEtleVZhbHVlPjxSU0FLZXlWYWx1ZT48TW9kdWx1cz5qNmp2OEdJNW00bFROc1J2eklJcHJvTWhpbVNDUTNkVmZFVE1WNzR1c1VPb1pNM3o4elMraUtpOEZ0VlN3MXA2VjNQMHdueWlqSFhacXZFT3M5RWJ2UjAzSEkxR3VydThkY0YyT0YwR1B4cHQxV1ZEaU1QNGg5TlhLOU83dnI5b0VIZm5mdlJrZjd1Z1B6V1lIWFRLUXdPb1pYR1d4QmpnVVlUQWQxUEx2Tjg9PC9Nb2R1bHVzPjxFeHBvbmVudD5BUUFCPC9FeHBvbmVudD48L1JTQUtleVZhbHVlPjwvS2V5VmFsdWU+PC9jOlB1YmxpY0tleT48YzpLZXlVc2FnZT48YzpFbmNyeXB0S2V5PjE8L2M6RW5jcnlwdEtleT48L2M6S2V5VXNhZ2U+PGM6U2VjdXJpdHlMZXZlbD4yMDAwPC9jOlNlY3VyaXR5TGV2ZWw+PGM6TWFudWZhY3R1cmVyRGF0YT48YzpNYW51ZmFjdHVyZXJOYW1lPkRpZ2l0YWw1PC9jOk1hbnVmYWN0dXJlck5hbWU+PGM6TWFudWZhY3
[2013/09/27 09:45:40] upnphttp.c:613: debug: SOAPAction: urn:microsoft.com:service:X_MS_MediaReceiverRegistrar:1#RegisterDevice
[2013/09/27 09:45:40] upnpsoap.c:1821: debug: SoapMethod: RegisterDevice
[2013/09/27 09:45:40] upnpsoap.c:1833: warn: SoapMethod: Unknown: RegisterDevice
[2013/09/27 09:45:40] upnpsoap.c:1881: warn: Returning UPnPError 401: Invalid Action
[2013/09/27 09:45:40] upnphttp.c:1157: debug: HTTP RESPONSE: HTTP/1.1 500 Internal Server Error
Content-Type: text/xml; charset="utf-8"
Connection: close
Content-Length: 398
Server: 3.2.0-3-amd64 DLNADOC/1.50 UPnP/1.0 MiniDLNA/1.1.0
Date: Fri, 27 Sep 2013 08:45:40 GMT
EXT:
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/" s:encodingStyle="http://schemas.xmlsoap.org/soap/encoding/"><s:Body><s:Fault><faultcode>s:Client</faultcode><faultstring>UPnPError</faultstring><detail><UPnPError xmlns="urn:schemas-upnp-org:control-1-0"><errorCode>401</errorCode><errorDescription>Invalid Action</errorDescription></UPnPError></detail></s:Fault></s:Body></s:Envelope>

The correct response, as far as I'm aware, should be to accept the registration and return an HTTP 200 response, rather than 500.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Florian W. (florian-will)]

According to http://sourceforge.net/p/minidlna/bugs/212/ , this should work since minidlna 1.1.2. So any trusty, utopic or vivid users should be fine.

Can anyone confirm so we can close this as "fix released"?