On 19/12/2018 04:58, Melvin wrote:
> Hi Christopher Schultz,
> *
> *
> I did not mean that the browser is throwing an error. My problem is that
> in 9.0.13 tomcat's error page is shown instead of my error page.
As Rémy has already explained:
- The URL is invalid
- Therefore, Tomcat reports an err
Hi Christopher Schultz,
I did not mean that the browser is throwing an error. My problem is that in
9.0.13 tomcat's error page is shown instead of my error page. I have given
error page location in web.xml. error.jsp is located in the root of my
webapp.
I know that if I add '^' in relaxedquerycha
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Melvin,
On 12/18/18 04:21, Melvin wrote:
> Tomcat 9.0.13 I switched from tomcat 8.5.35 to 9.0.13. In 8.5 when
> I send an unencoded character in queryString it throws 400 error in
> the browser itself and no Exception is thrown or seen explicitly.
Tomcat 9.0.13
I switched from tomcat 8.5.35 to 9.0.13. In 8.5 when I send an
unencoded character in queryString it throws 400 error in the browser
itself and no Exception is thrown or seen explicitly.
After I switched to tomcat 9, when I send an unencoded character in
queryString it throws Except
