2025-04-10, 05:04 PM
(This post was last modified: 2025-04-10, 05:05 PM by bitstream. Edited 1 time in total.)
Just for documentation in case someone else is running into the same problem: When setting
<RequireHttps>true</RequireHttps>
the DLNA plugin fails to start with this log entry:
[ERR] The DLNA specification does not support HTTPS.
This is because DLNA is using SSDP as communication protocol which again is nothing else then sending a HTTP header over UDP. Still, for me, it was unexpected since I thought RequireHttps is only used in the context of the UI to enforce secure communication, which makes sense on the UI as there are passwords transmitted from the client to the server. Since this is not the case with DLNA, it's kind of okish that DLNA is running on http. So it might be worth a thought to decouple RequireHttps from the DNLA plugin.
<RequireHttps>true</RequireHttps>
the DLNA plugin fails to start with this log entry:
[ERR] The DLNA specification does not support HTTPS.
This is because DLNA is using SSDP as communication protocol which again is nothing else then sending a HTTP header over UDP. Still, for me, it was unexpected since I thought RequireHttps is only used in the context of the UI to enforce secure communication, which makes sense on the UI as there are passwords transmitted from the client to the server. Since this is not the case with DLNA, it's kind of okish that DLNA is running on http. So it might be worth a thought to decouple RequireHttps from the DNLA plugin.