Differences of HandlerInterceptor & Filter

HandlerInterceptor is basically similar to a Servlet 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.

HandlerInterceptor与Servlet Filter基本上是相似的，不同的是，HandlerInterceptor仅允许进行pre-processing和post-processing。在pre-processing阶段可以阻止handler本身的执行。

Note that a filter gets configured in web.xml, a HandlerInterceptor in the application context.

Fliter在web.xml中进行配置，HandlerInterceptor在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 (e.g. images), or to all requests.

作为一个基本准则，与handler相关的细粒度的预处理任务是HandlerInterceptor实现的候选对象，尤其是抽取的handler公共处理代码和授权检查。
另一方面，Filter非常适合处理请求内容和视图内容，比如multipart表单和GZIP压缩。典型应用于需要将Filter映射到某些内容类型（比如图片）或所有请求的场景。

参考

Spring Interceptor vs Filter 拦截器和过滤器区别
SpringMVC中的Interceptor拦截器及与Filter区别
Spring Boot实战：拦截器与过滤器