Thank you for your answer, it hadn't occurred to me to try removing the jsp
mapping. Unfortunately it doesn't work...I removed it, and behavior stays the
same. I tried setting the STRICT_SERVLET_COMPLIANCE=true (hoping the strict
request wrapping rules would help), but no go.
This problem is a
2011/8/8 Nadav Katz nadav.k...@oracle.com:
Thank you for your answer, it hadn't occurred to me to try removing the jsp
mapping. Unfortunately it doesn't work...I removed it, and behavior stays the
same. I tried setting the STRICT_SERVLET_COMPLIANCE=true (hoping the strict
request wrapping
On 08/08/2011 08:47, Konstantin Kolinko wrote:
2011/8/8 Nadav Katz nadav.k...@oracle.com:
Thank you for your answer, it hadn't occurred to me to try removing the jsp
mapping. Unfortunately it doesn't work...I removed it, and behavior stays
the same. I tried setting the
I apologize for wasting everyone's time. Tomcat was working fine, it's just
that the applet requested the exact same servlet at the exact same time. This
is why I saw two different Request objects and why the filter intercepted the
request. Since I didn't notice that this happened, I confused
2011/8/8 Nadav Katz nadav.k...@oracle.com:
\
I have a filter in place for validating CSRF tokens. I only wish to validate
requests coming from the client, so no validation for dynamic includes or
forwards. My web.xml for the filter looks like this:
filter-mapping
