The following explanation can be extracted from Spring 's own documentation :
HandlerInterceptor is basically similar to a Servlet 2.3 Filter, but in contrast to the latter it just allows custom pre-processing with the option of prohibiting the execution of the handler itself, and custom post-processing. Filters are more powerful, for example they allow for exchanging the request and response objects that are handed down the chain. Note that a filter gets configured in web.xml, a HandlerInterceptor in the application context.
As a basic guideline, fine-grained handler-related preprocessing tasks are candidates for HandlerInterceptor implementations, especially factored-out common handler code and authorization checks. On the other hand, a Filter is well-suited for request content and view content handling, like multipart forms and GZIP compression. This typically shows when one needs to map the filter to certain content types (eg images), or to all requests.
What this means is that filters are more suitable for handling requests and content related to views, while interceptors are more suitable for pre-processing tasks, such as authentication checks.
One advantage interceptors have over filters is that they are able to intercept between the controller and the view's render. On the other hand interceptors are Beansfrom Spring, so you have access to the whole context from them.
The following explanation can be extracted from Spring 's own documentation :
What this means is that filters are more suitable for handling requests and content related to views, while interceptors are more suitable for pre-processing tasks, such as authentication checks.
One advantage interceptors have over filters is that they are able to intercept between the controller and the view's render. On the other hand interceptors are
Beansfrom Spring, so you have access to the whole context from them.