Kai == Kai Schliemann [EMAIL PROTECTED] writes:
I did something similar. I have an Apache serving static content, and
Tomcat for Jsp and servlets. Tomcat is hidden behind a firewall, the
webapp can only be seen through apache. So, to protect a directory
with, you only have to configure a
Hello list,
I have the following problem:
I'm running Apache 1.3.27 on Suse Linux 8.2 (Server 1) and Tomcat 4.1.24 on
Suse Linux 8.2 (Server 2).
I'm using mod_jk as connector for Apache/Tomcat which works fine without
SSL-configuration.
My JAVA-Webapp is running on Tomcat (Server 2).
I can
Hello list,
I have the following problem:
I'm running Apache 1.3.27 on Suse Linux 8.2 (Server 1) and Tomcat 4.1.24 on
Suse Linux 8.2 (Server 2).
I'm using mod_jk as connector for Apache/Tomcat which works fine without
SSL-configuration.
My JAVA-Webapp is running on Tomcat (Server 2).
I can
Easiest is probably to use a:
security-constraint
web-resource-collection
web-resource-nameSSL area/web-resource-name
url-pattern/online/*/url-pattern
/web-resource-collection
user-data-constraint
transport-guaranteeINTEGRAL/transport-guarantee
