Mike C;687211 Wrote:
> What kind of problems are you seeing from the MiniUPnPc/1.3 on
> 192.168.1.3?
> Closing that app fixed the problem...
The bug that I found in MiniUPnPc is that it does not comply to the
UPnP specifications; in the code below its SOAPAction header is non
compliant since it lacks a namespace prefix.
Code:
--------------------
192.168.1.3:64652 Recv : POST / HTTP/1.1
Host: 192.168.1.2:31416
User-Agent: Windows/1.3, UPnP/1.0, MiniUPnPc/1.3
Content-Length: 245
Content-Type: text/xml
SOAPAction: "#GetCommonLinkProperties"
Connection: Close
Cache-Control: no-cache
Pragma: no-cache
--------------------
However, MiniUPnPc is *not* the reason why Whitebear has problems in
your rig; the real reason is that the application is subscribing to all
event notification channels, as do both instances of JRMC. And Whitebear
is properly sending event notifications to all three subscribers, but it
turns out that some of the status changes behind the events are getting
cleared before Whitebear has sent all the notifications, so the last
subscriber is getting an "empty" notification. This is a bug in
Whitebear that I will fix in a forthcoming release.
--
AndrewFG
Regards,
AndrewFG
Try out Whitebear. The middleware that joins the two worlds of:
1. UPnP/DLNA media clients and media players, and,
2. Squeezebox Server and Squeeze Players
Download it for free here: http://www.whitebear.ch/mediaserver
------------------------------------------------------------------------
AndrewFG's Profile: http://forums.slimdevices.com/member.php?userid=15838
View this thread: http://forums.slimdevices.com/showthread.php?t=90842
_______________________________________________
discuss mailing list
[email protected]
http://lists.slimdevices.com/mailman/listinfo/discuss
