home
products
contribute
download
documentation
forum
Home
Forums
New posts
Search forums
What's new
New posts
All posts
Latest activity
Members
Registered members
Current visitors
Donate
Log in
Register
What's new
Search
Search
Search titles only
By:
New posts
Search forums
Search titles only
By:
Menu
Log in
Register
Navigation
Install the app
Install
More options
Contact us
Close Menu
Forums
MediaPortal 2
General
Unable to watch live TV Mediaplayer 2.1 Final
Contact us
RSS
JavaScript is disabled. For a better experience, please enable JavaScript in your browser before proceeding.
You are using an out of date browser. It may not display this or other websites correctly.
You should upgrade or use an
alternative browser
.
Reply to thread
Message
<blockquote data-quote="morpheus_xx" data-source="post: 1224767" data-attributes="member: 48495"><p>[USER=82144]@mm1352000[/USER] The posted errors above are coming out of our UPnP library.</p><p></p><p>The cause are missing <a href="https://github.com/MediaPortal/MediaPortal-2/blob/ffe1d6090fa28fcae9c2cc61415e23be02fc5670/MediaPortal/Source/Core/UPnP/Infrastructure/CP/SSDP/SSDPClientController.cs#L646-L648" target="_blank">header entries</a> </p><p>[CODE=CSHARP] string bi = header["BOOTID.UPNP.ORG"];</p><p> string ci = header["CONFIGID.UPNP.ORG"];</p><p> string sp = header["SEARCHPORT.UPNP.ORG"];[/CODE]</p><p>that are checked against <a href="https://github.com/MediaPortal/MediaPortal-2/blob/ffe1d6090fa28fcae9c2cc61415e23be02fc5670/MediaPortal/Source/Core/UPnP/Infrastructure/CP/SSDP/SSDPClientController.cs#L783-L788" target="_blank">here</a>.</p><p></p><p>The incoming SSDP responses look like:</p><p>[CODE][2017-06-20 07:54:56,183] [3375 ] [31 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:</p><p>HTTP/1.1 200 Ok</p><p>CACHE-CONTROL: max-age=1800</p><p>DATE: Mon, 19 Jun 2017 21:54:58 GMT</p><p>EXT:</p><p>LOCATION: http://192.168.2.1:1780/WFADevice2.xml</p><p>SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00</p><p>ST: urn:schemas-wifialliance-org:device:WFADevice:1</p><p>USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:device:WFADevice:1</p><p></p><p></p><p>[2017-06-20 07:54:56,183] [3375 ] [31 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:</p><p>HTTP/1.1 200 Ok</p><p>CACHE-CONTROL: max-age=1800</p><p>DATE: Mon, 19 Jun 2017 21:54:58 GMT</p><p>EXT:</p><p>LOCATION: http://192.168.2.1:1780/WFADevice2.xml</p><p>SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00</p><p>ST: upnp:rootdevice</p><p>USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::upnp:rootdevice</p><p></p><p></p><p>[2017-06-20 07:54:56,184] [3376 ] [52 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message:</p><p>HTTP/1.1 200 Ok</p><p>CACHE-CONTROL: max-age=1800</p><p>DATE: Mon, 19 Jun 2017 21:54:58 GMT</p><p>EXT:</p><p>LOCATION: http://192.168.2.1:1780/WFADevice2.xml</p><p>SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00</p><p>ST: urn:schemas-wifialliance-org:service:WFAWLANConfig:1</p><p>USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:service:WFAWLANConfig:1</p><p></p><p></p><p>[/CODE]</p><p>So they are not part of our code.</p><p></p><p><strong>Question is</strong>: are those 3 headers mandatory in all cases? Could we allow them to be null to detect more devices? Especially if the UPnP library is used for non-MP2 services...</p><p></p><p>Note to [USER=74879]@HTPCSourcer[/USER] the logging in DEBUG mode was only added to trace exactly that kind of format issues. They should not affect MP functions, our services are working to our rules <img src="data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7" class="smilie smilie--sprite smilie--sprite2" alt=";)" title="Wink ;)" loading="lazy" data-shortname=";)" /></p><p>Only negative aspect now is, that they are causing quite lot logging overhead (in DEBUG level only!)</p></blockquote><p></p>
[QUOTE="morpheus_xx, post: 1224767, member: 48495"] [USER=82144]@mm1352000[/USER] The posted errors above are coming out of our UPnP library. The cause are missing [URL='https://github.com/MediaPortal/MediaPortal-2/blob/ffe1d6090fa28fcae9c2cc61415e23be02fc5670/MediaPortal/Source/Core/UPnP/Infrastructure/CP/SSDP/SSDPClientController.cs#L646-L648']header entries[/URL] [CODE=CSHARP] string bi = header["BOOTID.UPNP.ORG"]; string ci = header["CONFIGID.UPNP.ORG"]; string sp = header["SEARCHPORT.UPNP.ORG"];[/CODE] that are checked against [URL='https://github.com/MediaPortal/MediaPortal-2/blob/ffe1d6090fa28fcae9c2cc61415e23be02fc5670/MediaPortal/Source/Core/UPnP/Infrastructure/CP/SSDP/SSDPClientController.cs#L783-L788']here[/URL]. The incoming SSDP responses look like: [CODE][2017-06-20 07:54:56,183] [3375 ] [31 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message: HTTP/1.1 200 Ok CACHE-CONTROL: max-age=1800 DATE: Mon, 19 Jun 2017 21:54:58 GMT EXT: LOCATION: http://192.168.2.1:1780/WFADevice2.xml SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00 ST: urn:schemas-wifialliance-org:device:WFADevice:1 USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:device:WFADevice:1 [2017-06-20 07:54:56,183] [3375 ] [31 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message: HTTP/1.1 200 Ok CACHE-CONTROL: max-age=1800 DATE: Mon, 19 Jun 2017 21:54:58 GMT EXT: LOCATION: http://192.168.2.1:1780/WFADevice2.xml SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00 ST: upnp:rootdevice USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::upnp:rootdevice [2017-06-20 07:54:56,184] [3376 ] [52 ] [DEBUG] - SSDPClientController: Cannot handle SSDP response from 192.168.2.1:1900 - Invalid message: HTTP/1.1 200 Ok CACHE-CONTROL: max-age=1800 DATE: Mon, 19 Jun 2017 21:54:58 GMT EXT: LOCATION: http://192.168.2.1:1780/WFADevice2.xml SERVER: POSIX/1.0 UPnP/1.1 UPnP Stack/v1.00 ST: urn:schemas-wifialliance-org:service:WFAWLANConfig:1 USN: uuid:31da958f-40ad-5935-da37-a457b8e519c9::urn:schemas-wifialliance-org:service:WFAWLANConfig:1 [/CODE] So they are not part of our code. [B]Question is[/B]: are those 3 headers mandatory in all cases? Could we allow them to be null to detect more devices? Especially if the UPnP library is used for non-MP2 services... Note to [USER=74879]@HTPCSourcer[/USER] the logging in DEBUG mode was only added to trace exactly that kind of format issues. They should not affect MP functions, our services are working to our rules ;) Only negative aspect now is, that they are causing quite lot logging overhead (in DEBUG level only!) [/QUOTE]
Insert quotes…
Verification
Post reply
Forums
MediaPortal 2
General
Unable to watch live TV Mediaplayer 2.1 Final
Contact us
RSS
Top
Bottom