I didn't spend too long on this, as we only needed the vhosts as a stop-gap
solution, and only needed three at that, but the only way I found to do it
was to have vhosts defined in both Apache and Tomcat.
Apache's vhosting knows the difference for the static pages, and any
.jsps/servlets for
I would suggest that Apache is also more secure - it's been around longer,
and has had more development, thus has had longer to mature. If you hide
Tomcat behind Apache, then any bugs that may appear in Tomcat's URL parsing
(for example) are less of a worry.
Duncan.
-Original
I'm sure someone will jump on this from a great height if I'm wrong, but I
seem to recall that the cache settings are for intermediate caches - not the
browser. The browser can cache pages as it sees fit - provided that it
checks to see if they've been updated, but the cache control settings are
Hi all,
I've been merrily using Tomcat for some time now (v3.2.1) and have
just come accross a rather bizarre one... Jasper seems to 'forget' the
classpath after a while and refuses to compile new JSPs. All is well after
startup, things run smoothly for an hour or two, and Tomcat will
