Day: November 5, 2012

As its very known that websites are secured with SSL certificates and thus run as HTTPS secured web sites, it’s interesting to know what happens if that securing SSL certificate is expired.   In short: For a certificate expired websites, browsers will notify users with a security alert prompt.  If you choose to agree to accept this certificate you will be able to enter the secure site, providing it is indeed a secure and valid site, and not an exploit or a redirected malicious site. SSL (secure socket layer) is responsible for maintaining an encrypted session between the web server […]

It’s possible that many of the websites are “hosted in Tomcat” and yet “fronted by IIS” and vice-versa.  The primary reason for this is that normally IIS can not execute Servlets and Java Server Pages (JSPs), configuring IIS to use the JK ISAPI redirector plugin will let IIS send servlet and JSP requests to Tomcat (and this way, serve them to clients).     Reference: < p>The Apache Tomcat Connector – Webserver HowTo – IIS HowTo

Tomcat and SSL It is important to note that configuring Tomcat to take advantage of secure sockets is usually only necessary when running it as a standalone web server. When running Tomcat primarily as a Servlet/JSP container behind another web server, such as Apache or Microsoft IIS, it is usually necessary to configure the primary web server to handle the SSL connections from users. Typically, this server will negotiate all SSL-related functionality, then pass on any requests destined for the Tomcat container only after decrypting those requests. Likewise, Tomcat will return clear-text responses, which will then be encrypted by the […]