Hi Christopher,
Thanks for the suggestion. But I don't have the luxury of using a Load
balancer or Proxy. I kind of agree that it would be best to handle outside
tomcat.
At this point, it is working as expected after all changes mentioned in the
thread. Again, I value your opinion and feedback.
Bhavesh,
On 10/10/22 22:05, Bhavesh Mistry wrote:
I figured out the issue by default *mapperContextRootRedirectEnabled is
true* hence it was redirecting it. By setting it false, I was able to get
controller to filter.
At the risk of complicating things, if I were you I would handle this
com
I figured out the issue by default *mapperContextRootRedirectEnabled is
true* hence it was redirecting it. By setting it false, I was able to get
controller to filter.
wrote:
> Hi Mark ,
>
> Thank you for your feedback. I have made all the changes needed and it is
> working as expected except
Hi Mark ,
Thank you for your feedback. I have made all the changes needed and it is
working as expected except for ONE use case where the servlet context path
does not end with */*. When server context path is given without /
('/versa'), tomcat seems to do 302 redirect to automatically '/versa/
On 07/10/2022 19:47, Bhavesh Mistry wrote:
Hi Mark,
Thank you for your quick response. Your proposed solution works by
removing the transport-guarantee element. Another quick question, I have
Connection has a property called allowTrace method. Is it possible to
configure TOMCAT Connector to di
Hi Mark,
Thank you for your quick response. Your proposed solution works by
removing the transport-guarantee element. Another quick question, I have
Connection has a property called allowTrace method. Is it possible to
configure TOMCAT Connector to disallow TRACE,OPTIONS,HEAD,CONNECT rather
than
On 07/10/2022 18:09, Bhavesh Mistry wrote:
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method
on port 80 and 443.
We have connector definitions as follows:
-->
-->
and we have an application filter to block and r
Hi Tomcat Team,
We have a unique situation. We wanted to block ALL *OPTIONALS* HTTP method
on port 80 and 443.
We have connector definitions as follows:
-->
-->
and we have an application filter to block and return 405. This works for
HTTPS port 443. But req