05-02-2019, 10:38 PM
Hi,
Use of HTTPS/TLS protocol does not really involve DNS. Its use is negotiated during the connection request from client Browser to Web server.
moOde uses NGINX Web server and so this is the component that would need to be configured for HTTPS/TLS.
http://nginx.org/en/docs/http/configurin...rvers.html
Some of the challenges are:
- Unless the TLS Certificate is from a "well known CA" the Browser will display warning dialogs to the user.
- There is an ongoing cost to using a Cert from a well known CA that includes the initial cost plus the periodic renewal cost.
- There is a performance penalty incurred as a result of the encryption process
-Tim
Use of HTTPS/TLS protocol does not really involve DNS. Its use is negotiated during the connection request from client Browser to Web server.
moOde uses NGINX Web server and so this is the component that would need to be configured for HTTPS/TLS.
http://nginx.org/en/docs/http/configurin...rvers.html
Some of the challenges are:
- Unless the TLS Certificate is from a "well known CA" the Browser will display warning dialogs to the user.
- There is an ongoing cost to using a Cert from a well known CA that includes the initial cost plus the periodic renewal cost.
- There is a performance penalty incurred as a result of the encryption process
-Tim
