Spring HandlerInterceptor vs Servlet 过滤器

Question

HandlerInterceptor Spring 中的 s 现在可以使用 <mvc:interceptors> 配置为仅在某些 URL 上调用.

Servlet 过滤器可以实现相同的功能(日志记录、安全等)。那么应该使用哪一个呢？

我认为对于拦截器，可以使用 ModelAndView对象与模型一起工作，因此它具有更多优势。谁能画出过滤器或拦截器比另一个有优势的场景？

Answer 1

org.springframework.web.servlet.HanderInterceptor 接口(interface)JavaDoc本身有两段讨论这个问题:

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 (e.g. images), or to all requests.