## 自定義過濾器 模擬一個登錄的校驗。基本邏輯：如果請求中有access-token參數，則認為請求有效，放行。 ~~~ package com.like.filter; import com.netflix.zuul.ZuulFilter; import com.netflix.zuul.context.RequestContext; import com.netflix.zuul.exception.ZuulException; import org.apache.commons.lang.StringUtils; import org.springframework.cloud.netflix.zuul.filters.support.FilterConstants; import org.springframework.http.HttpStatus; import org.springframework.stereotype.Component; import javax.servlet.http.HttpServletRequest; @Component public class LoginFilter extends ZuulFilter { @Override public String filterType() { return FilterConstants.PRE_TYPE; //定義為前置過濾器 } @Override public int filterOrder() { return FilterConstants.PRE_DECORATION_FILTER_ORDER - 1; //在處理請求頭之前進行攔截 } @Override public boolean shouldFilter() { return true; //開啟過濾器 } @Override public Object run() throws ZuulException { //獲取請求上下文,此作用域范圍:從請求到達zuul一直到路由結束后返回給客戶端這個完整流程.但是它不會存在微服務內,只存在zuul中 RequestContext context = RequestContext.getCurrentContext(); //獲取request HttpServletRequest request = context.getRequest(); //獲取請求參數 String token = request.getParameter("access-token"); //判斷是否存在 if (StringUtils.isBlank(token)) { //不存在,未登錄,進行攔截 context.setSendZuulResponse(false); context.setResponseStatusCode(HttpStatus.FORBIDDEN.value()); } return null; } } ~~~ ## 測試 不帶access-token參數:  攜帶access-token參數: