I've been getting a good amount of emails regarding the clustering system
being broken in Tomcat 5.5, so I thought I make the announcement here so
that we can clear the air once and for all.
In tomcat 5.5.10 the underlying communication protocol for the clustering
system changed, and not only made
use mod_proxy, much easier, and in our tests has proven to scale better,
and you will wanna look for a directive called ProxyHostPreserve so that
request.getServerName returns the right name,
then the IP address will be stored in x-forwarded-for header in the HTTP
request.
Filip
> Hello Everyone,
you scanner "may not work so well", it thinks that Tomcat is Apache httpd,
The warnings you see, and the suggested fix, are related to
httpd.apache.org, not tomcat.apache.org
two different prouducts
> Hello,
>
> We just installed a JBOSS server in our production Environment...
> Apparently JBOSS
what version of Tomcat and what are the logs saying?
Filip
Quoting Jim Reynolds <[EMAIL PROTECTED]>:
After creating a new Host, I now want to set up SSL on it. Following
the docs I did the following:
1) create keystore
E:\Tomcat\bin\DEVKEY>keytool -genkey -alias tomcat -keyalg RSA
-keystore E
hi Sushil
that scenario works just fine for me. you would have to show your actual
code (and a test case) for me to analyze your actual problem
Filip
Sushil Vegad wrote:
> Hello Filip,
>
> Please let me know your thoughts on this.
>
> Our scenario is:
> We set the username in the cookie when the
