springcloud zuul搭建伺服器介面閘道器
阿新 • • 發佈:2019-01-28
加入依賴;
<dependency>
<groupId>org.springframework.cloud</groupId>
<artifactId>spring-cloud-starter-zuul</artifactId>
</dependency>
配置application.yml;
eureka: client: service-url: defaultZone: http://localhost:8080/eureka/ server: port: 8765 spring: application: name: service-zuul zuul: routes: api-a: path: /api-member/** service-id: service-member api-b: path: /api-order/** service-id: service-order
建立啟動器;
@EnableZuulProxy
@EnableEurekaClient
@SpringBootApplication
public class ZullApplication {
public static void main(String[] args) {
SpringApplication.run(ZullApplication.class, args);
}
}
根據在application.yml中的配置,將在eureka中註冊的服務包裝,攔截請求,
根據配置轉發到實際地址,解決跨域問題
zuul閘道器攔截引數:
定義一個zuulfilter:
@Component
public class MyFilter extends ZuulFilter{
private static Logger log = LoggerFactory.getLogger(MyFilter.class);
@Override
public String filterType() {
return "pre";
}
@Override
public int filterOrder() {
return 0;
}
@Override
public boolean shouldFilter () {
return true;
}
@Override
public Object run() {
RequestContext ctx = RequestContext.getCurrentContext();
HttpServletRequest request = ctx.getRequest();
log.info(String.format("%s >>> %s", request.getMethod(), request.getRequestURL().toString()));
Object accessToken = request.getParameter("token");
if(accessToken == null) {
log.warn("token is empty");
ctx.setSendZuulResponse(false);
ctx.setResponseStatusCode(401);
try {
ctx.getResponse().getWriter().write("token is empty");
}catch (Exception e){}
return null;
}
log.info("ok");
return null;
}
}
filterType:返回一個字串代表過濾器的型別,在zuul中定義了四種不同生命週期的過濾器型別,具體如下:
- pre:路由之前
- routing:路由之時
- post: 路由之後
- error:傳送錯誤呼叫
- filterOrder:過濾的順序
- shouldFilter:這裡可以寫邏輯判斷,是否要過濾,本文true,永遠過濾。
- run:過濾器的具體邏輯。可用很複雜,包括查sql,nosql去判斷該請求到底有沒有許可權訪問。
token is empty
正常顯示