Yes, you can run https with Tomcat versions 3 and 4 - it's documented fairly well at the jakarta tomcat website. In the case of running Tomcat through another web server such as IIS or Apache, the actual https is usually handled by the front-side web server and the web-server/tomcat pipeline may be insecure (decrypted), so you want to make sure that the firewall blocks direct access. You'd usually want to anyway.
Customer surveys are for companies who didn't pay proper attention to begin with.
Hi Ashik Not sure how https got wrapped up into a discussion of SSI (Server Side Includes ) Looking at Java Examples in a Nutshell, Dave Flanagan states Tomcat 3.X doesn't support server-side includes (SSI)(p. 467) Jason Hunter's book also confirms this (p. 14) So it seems you can't do .shtml through Tomcat Also I noted this question has been asked here as well... all the best - Jim
- Jim Petersen <br />SCJP2<br />SCWCD<p>- but then again, I could be wrong...
Oops. Sometimes "SSI" and "SSL" get crossed. It's easy to misread "shtml" as "Secure HTML". Either that or maybe there's dirt on the screen near the base of the "I"_ Of course, SSI Apache-style is pointless, since JSP's have an "include" facility that's as good or better. If you simply want SSI-type operations on ".shtml" pages, you can either: A) front Tomcat with Apache (the high-performance approach) B) Setup Tomcat's web.xml to interpret shtml's into JSP's (the sneaky approach)