Read the statement by Michael Teeuw here.
Force client https with server https already setup
I have a server with MM Server set up ready. I can access it with my browser via https serverd by nginx reverse proxy.
The problem is when I want to use it on the client, by doing
node clientonly --address mymm.xxx.com --port xxx, it says
Syntax Error: Unexpected tocken < html>. I guess it is caused by my https redirects. If my reverse proxy recieve http request it will redirect http request to https via 307 code.
So I changed the
--address https://mymm.xxx.com, this time it says
http://https://mymm.xxx.com. Well, ok. I guess no way to use https?
I can start the MM by using Firefox
-kioskoption but it is also buggy, can’t promise it will go fullscreen 100%.
And idea how to run my client with node via https? Or i really have to use the plain http?
@sdetweil Thanks for replying
It seems chromium’s
-kioskoption works better than Firefox. When I use Firefox it has quite a chance not actully going full screen. I think my problem is no more now.