SSDP: SERVER cannot be decoded successfully

Serviio-v1.9 on Windows10 64bit
Microsoft Message Analyzer v1.4

While working on a network routing issue from wired to wireless LAN, I was watching the packets for udp port 1900 with Microsoft Message Analyzer. It notified that there was a problem with the packets stating that the SSDP: SERVER field cannot be decoded successfully due to field value does not follow RFC.

It is odd that it states "RFC", when SSDP was never in a RFC, but rather an ietc-draft, which was retired and later folded into the UPNP specification.

Looking at the SERVER header, I'm thinking it might be missing a comma:

OLD: Windows 10, UPnP/1.0 DLNADOC/1.50, Serviio/1.9
NEW: Windows 10, UPnP/1.0, DLNADOC/1.50, Serviio/1.9

I have posted a screenshot at: https://drive.google.com/file/d/0B9L0eDJu-2GMdTA1VXhhSUFTa1E/view?usp=sharing

FWIW, I was trying to debug why my Samsung PN64D8000 wasn't seeing the Serviio announcements anymore. I have serviio.advertisementDuration set to 30.

After further testing, I enabled the DLNA server in Plex, and the TV is able to access it through Samsung's AllShare.

I'm thinking that Samsung's AllShare is being really picky about the SSDP protocol and is punting Serviio's SSDP NOTIFY announcements.

[zip]

Do you have an example of what Plex uses as the SERVER header?

I may have been wrong about the commas. This is what Plex sends:

  Code:

UPnP/1.0 DLNADOC/1.50 Platinum/1.0.5.13

Microsoft Message Analyzer gives the Plex SSDP packet a clean bill of health.

[zip]

yeah, I removed the commas from the string and it'll be in 1.9.1