如何处理Filters中抛出的异常？

Question

I am using Spring 4 and Tomcat. The issue is sometimes I have to throw a (custom) RuntimeException in my filter (The control has not even reached the controller). The issue is since I am not throwing an exception that tomcat understands, it gets converted to 500 (internal server error). I believe a 403 Forbidden would be better than a 500 (For my custom exception). I have looked at @ExceptionHandler and @ControllerAdvice annotations. But these work only if the control reaches the controller.

As of now I am manually setting the status to 403 in the HTTPResponse in my filter. Is there a better way of handling this scenario?

Answer 1

you should use something like this

Setting an error handler in web.xml

<error-page>
    <exception-type>java.lang.RuntimeException</exception-type>
    <location>/handleExceptionService</location>
</error-page>

So, when you reach your service, yo can do wathever you want with the error.

Good Luck!!!

Answer 2

You can add in web.xml
<error-page>
    <error-code>404</error-code> 
    <location>/error-404.html</location>
</error-page> 
<error-page>
    <error-code>403</error-code> 
    <location>/access_denied.html</location>
</error-page>