06-08-2018 03:19 AM - edited 03-21-2019 09:12 AM
I'm trying to load a simple xml from https://192.168.1.21/test/menu.xml and it doesn't work.
If I load the same url from http it does work, what is the problem with https?
PS: Syslog is attached
PS2: More info here.
Solved! Go to Solution.
06-14-2018 04:56 AM - edited 06-14-2018 05:00 AM
The LAN use the DNS from the telephony/internet provider, it would be annoying to set a local DNS server for only a single entry.
The only clients will be phones, Firefox and Chrome.
Firefox and Chrome can use the server perfectly from both IP (https://192.168.1.21/) and Windows computer name (https://reception/) and certificate validate perfectly in both cases using SNA so Subject is useless in these cases.
The problem of the phone is that it cannot access
https://reception/
also from normal http.
06-14-2018 05:18 AM
it would be annoying to set a local DNS server for only a single entry.
You are using technology (SSL) known to work better with DNS names, so for the sake of reliability, you should consider to have working one.
Just my recommendation. The final decision is sovereignty of particular responsible person.
The problem of the phone is that it cannot access
https://reception/
also from normal http.
No way to work as long as there's no DNS server willing to resolve reception name into IP address.
06-14-2018 05:26 AM - edited 06-14-2018 05:27 AM
Well, I cannot expect it supporting a Windows workgroup.
I have to thought about it.
But besides that it still would be nice to have a complete SNA support.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide