Thanks for reply!
We did changes in /conf/web.xml.
But when the changes did not reflect, we made changes in specific app as
well. But we could not see the cookie as secure.
We verified by the response headers seen in chrome developer tool. The
cookie JSESSIONID does not have a secure flag.
By th
Thanks Mark!
It works fine after removing packetSize.
On Fri, 1 Jan 2021, 3:18 pm Mark Thomas, wrote:
> You have only changed the packet size on the Tomcat side of the
> connection. The httpd side is still using 8192. That will work up until
> the point where Tomcat needs to return a response bi
You have only changed the packet size on the Tomcat side of the
connection. The httpd side is still using 8192. That will work up until
the point where Tomcat needs to return a response bigger than 8192
bytes. At which point it will fail. I suspect the response in the Tomcat
8 case was just less th
Here is the configuration details:
Apache:
> ProxyPass /app ajp://:8009/app retry=0 ttl=6000
> ProxyPassReverse /app ajp://:8009/app
> ProxyPreserveHost On
> ProxyRequests Off
> UseCanonicalName On
> Timeout 1200
> ProxyTimeout 1200
Tomcat 9:
> packetSize="65536"
> connectionTimeout="6" m