Hi chris,
Many thanks!
That's the solution.
Bernd
I wonder if the F5 is not happy with the HTTP response status "reason
string" being removed:
https://bz.apache.org/bugzilla/show_bug.cgi?id=60362
What happens if you add the sendReasonPhrase="true" to your
configuration and try again?
--
description
The requested resource is not available.
Apache Tomcat/8.0.45
and changed a bit in 8.5, but there is definelty no check on the
content, because i created a empty index.html, then the resp
>Are you actually using AJP between F5 and Tomcat? I would find that an
>unusual setup... usually F5 -> Tomcat would be HTTP(S).
I don't know if this connector is needed (maybe for https session
stickyness - i don't know how it is working exactly) I just tested any
port/conne
take
it off the server farms first? Or did you do it without?
Try to remove the affected tomcat off the server farm. Do you upgrade, and
then put it back inside the farm.
Or have you tried this already?
On 31 July 2017 at 17:59, Bernd Wahlen
wrote:
We are running a cluster of 5 tomcats behind
a
to LegacyCookieProcessor
but no success.
Any idea what to i can check or what changed related
to that problem?
Many thanks in advance,
Bernd Wahlen
K2 Interactive GmbH
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.
