<div>
What about installing a self signed certificate. &nbsp; I think the warning will only come up once.
</div>


What about installing a self signed certificate.   I think the warning will only come up once.

<div>
We are already using a self-signed certificate and you're correct about the warning only coming up once (unless the browser data is cleared), but that is the situation I'm trying to more elegantly handle.
</div>


We are already using a self-signed certificate and you're correct about the warning only coming up once (unless the browser data is cleared), but that is the situation I'm trying to more elegantly handle.

<div>
<div class="content wysiwyg-content">
I work for a company that ships data storage appliances with a GUI web application and several rest API services that the GUI web app talks to through SSL. Because each customer has a different domain, the SSL warning comes up in the browser. So the customer has to hit each rest API service first, click OK for the SSL warning, and only then will the entire application work. My question is if there is some way to facilitate this process where if the customer hits the front end web app first, we can detect that the warning is occurring with the rest API services and maybe bring up a separate window to allow the user to click OK for the warning.
</div>
</div>


I work for a company that ships data storage appliances with a GUI web application and several rest API services that the GUI web app talks to through SSL. Because each customer has a different domain, the SSL warning comes up in the browser. So the customer has to hit each rest API service first, click OK for the SSL warning, and only then will the entire application work. My question is if there is some way to facilitate this process where if the customer hits the front end web app first, we can detect that the warning is occurring with the rest API services and maybe bring up a separate window to allow the user to click OK for the warning.

Detect ssl warning message

HTTPS is a protocol for secure communication over a computer network which is widely used on the Internet. HTTPS consists of communication over Hypertext Transfer Protocol (HTTP) within a connection encrypted by Transport Layer Security (TLS) or its predecessor, Secure Sockets Layer (SSL). The main motivation for HTTPS is authentication of the visited website and to protect the privacy and integrity of the exchanged data. HTTPS is widely used for protecting page authenticity on all types of websites, securing accounts and keeping user communications, identity and web browsing private.

SSL / HTTPS

Web development includes all aspects of presenting content on intranets and the Internet, including delivery development, protocols, languages and standards, server software, browser clients, databases and multimedia generation.

Web Development

An application server is a software framework that provides both facilities to create applications and a server environment to run them. Most application server frameworks contain a comprehensive service layer model, acting as a set of components accessible to the software developer through an API defined by the platform itself. For Web applications, these components are usually performed in the same running environment as their web server(s), and their main job is to support the construction of dynamic pages. However, many application servers target much more than just Web page generation: they implement services like clustering, fail-over, and load-balancing.