详述SpringMVC中拦截器

目录

一、拦截器是什么？

二、拦截器生命周期

（1）实现拦截器的两种方式：

（2）拦截器中的方法：

preHandle方法：

postHandle方法：

afterCompletion方法：

（3）拦截器配置：

三、总结

---

一、拦截器是什么？

拦截器，顾名思义，是用于拦截客户端特定的请求的类。

二、拦截器生命周期

（1）实现拦截器的两种方式：

a.定义的Interceptor类要实现了Spring的HandlerInterceptor 接口

b.继承实现了HandlerInterceptor接口的类，比如Spring已经提供的实现了HandlerInterceptor接口的抽象类HandlerInterceptorAdapter

（2）拦截器中的方法：

preHandle方法：

加了“pre”后缀，即在处理请求前执行的方法，即无论请求是否被拦截，该方法都会被先执行，该方法用于对用户发出的请求进行预处理，在SpringMVC中，程序员可以定义多个interceptor，而在请求到达服务器端时，多个interceptor会按照生命顺序依次限制性preHandle方法，该方法的返回值为Boolean型，若为false，则后面的interceptor的preHandle方法都不再执行，请求终止；若为true，则继续执行postHandle方法和Controller方法。查看源码，原理如下：

DispatcherServlet类中doDispatch方法（注意注释内容）：

protected void doDispatch(HttpServletRequest request, HttpServletResponse response) throws Exception {
    HttpServletRequest processedRequest = request;
    HandlerExecutionChain mappedHandler = null;
    boolean multipartRequestParsed = false;

    WebAsyncManager asyncManager = WebAsyncUtils.getAsyncManager(request);

    try {
        ModelAndView mv = null;
        Exception dispatchException = null;

        try {
            processedRequest = checkMultipart(request);
            multipartRequestParsed = (processedRequest != request);

            // Determine handler for the current request.
            mappedHandler = getHandler(processedRequest);
            if (mappedHandler == null || mappedHandler.getHandler() == null) {
                noHandlerFound(processedRequest, response);
                return;
            }

            // Determine handler adapter for the current request.
            HandlerAdapter ha = getHandlerAdapter(mappedHandler.getHandler());

            // Process last-modified header, if supported by the handler.
            String method = request.getMethod();
            boolean isGet = "GET".equals(method);
            if (isGet || "HEAD".equals(method)) {
                long lastModified = ha.getLastModified(request, mappedHandler.getHandler());
                if (logger.isDebugEnabled()) {
                    logger.debug("Last-Modified value for [" + getRequestUri(request) + "] is: " + lastModified);
                }
                if (new ServletWebRequest(request, response).checkNotModified(lastModified) && isGet) {
                    return;
                }
            }

            if (!mappedHandler.applyPreHandle(processedRequest, response)) {//有此处代码结构可知，当applyPreHandle的返回值为false时，执行return，doDispatch方法结束，请求结束
                return;
            }

            // Actually invoke the handler.
            mv = ha.handle(processedRequest, response, mappedHandler.getHandler());

            if (asyncManager.isConcurrentHandlingStarted()) {
                return;
            }

            applyDefaultViewName(processedRequest, mv);
            mappedHandler.applyPostHandle(processedRequest, response, mv);
        }
        catch (Exception ex) {
            dispatchException = ex;
        }
        catch (Throwable err) {
            // As of 4.3, we're processing Errors thrown from handler methods as well,
            // making them available for @ExceptionHandler methods and other scenarios.
            dispatchException = new NestedServletException("Handler dispatch failed", err);
        }
        processDispatchResult(processedRequest, response, mappedHandler, mv, dispatchException);
    }
    catch (Exception ex) {
        triggerAfterCompletion(processedRequest, response, mappedHandler, ex);
    }
    catch (Throwable err) {
        triggerAfterCompletion(processedRequest, response, mappedHandler,