I think you should have searched better, because this seems like a duplicate entry to me.
AFAIK the players don't communicate with LMS over HTTP. This interface is really only to allow you to control what is being played. The main point about using plain HTTP here instead of secure HTTPS is that it doesn't require a (commercial) certificate and because of this *every* home appliance that offers some web based interface will use plain HTTP. The thing here is that HTTPS is difficult and requires maintenance that a regular home user shouldn't and doesn't want to be bothered with. As such it would amaze me very much if Chrome would enforce HTTPS and by doing so make communication with such home appliances impossible. If you are willing to do the effort of maintaining the validity of the HTTPS certificate it is not that big a deal though. Simply place LMS behind a HTTP(S) proxy (e.g. lighttp, nginx, apache), but do note that these web server applications may (by default) prohibit some of the URI strings used by the LMS frontend. For instance if you use Apache frontend then some of the images will not be displayed unless you specify the override `AllowEncodedSlashes NoDecode` in the server config. ------------------------------------------------------------------------ gordonb3's Profile: http://forums.slimdevices.com/member.php?userid=71050 View this thread: http://forums.slimdevices.com/showthread.php?t=115555 _______________________________________________ discuss mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/discuss
