I'm a little bit confused about Filter and Interceptor purposes.
As I understood from docs, Interceptor is run between requests. On the other hand Filter is run before rendering view, but after Controller rendered response.
So where is the difference between postHandle() in Interceptor and doFilter() in Filter?
What is the best practise in which use cases it should be used?
In this picture where works Filters and Interceptors?
Filter: - A filter as the name suggests is a Java class executed by the servlet container for each incoming HTTP request and for each HTTP response. This way is possible to manage HTTP incoming requests before they reach the resource, such as a JSP page, a servlet or a simple static page; in the same way, is possible to manage HTTP outbound response after resource execution.
Interceptor: - Spring Interceptors are similar to Servlet Filters but they act in Spring Context so are powerful to manage HTTP Request and Response but they can implement more sophisticated behaviour because can access all Spring context.
From baeldung:
Filters intercept requests before they reach the DispatcherServlet, making them ideal for coarse-grained tasks such as:
Authentication
Logging and auditing
Image and data compression
Any functionality we want to be decoupled from Spring MVC
HandlerIntercepors, on the other hand, intercepts requests between the DispatcherServlet and our Controllers. This is done within the Spring MVC framework, providing access to the Handler and ModelAndView objects. This reduces duplication and allows for more fine-grained functionality such as:
Handling cross-cutting concerns such as application logging
Detailed authorization checks
Manipulating the Spring context or model