Zuul API路由网关服务简介java
如图:这里的API 路由网关服务 由Zuul实现,主要就是对外提供服务接口的时候,起到了请求的路由和过滤做用,也所以可以隐藏内部服务的接口细节,历来有利于保护系统的安全性web
Zuul 路由配置spring
咱们新建一个module microservice-zuul-3001apache
这里咱们的zuul也注册到eureka服务里,端口3001;json
咱们修改下Hosts,专门为zuul搞个本地域名映射 浏览器
hosts文件 加下:安全
127.0.0.1 zuul.lingerqi.comapp
pom依赖:maven
<?xml version="1.0" encoding="UTF-8"?> <project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd"> <parent> <artifactId>testSpringcloud</artifactId> <groupId>com.lingerqi</groupId> <version>1.0-SNAPSHOT</version> </parent> <modelVersion>4.0.0</modelVersion> <artifactId>microservice-zuul-3001</artifactId> <properties> <java.version>1.8</java.version> </properties> <dependencies> <dependency> <groupId>com.lingerqi</groupId> <artifactId>microservice-common</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-web</artifactId> </dependency> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-test</artifactId> <scope>test</scope> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-eureka</artifactId> </dependency> <!-- actuator监控 --> <dependency> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-starter-actuator</artifactId> </dependency> <!-- hystrix容错 --> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-hystrix</artifactId> </dependency> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-config</artifactId> </dependency> <!--zuul网关--> <dependency> <groupId>org.springframework.cloud</groupId> <artifactId>spring-cloud-starter-zuul</artifactId> </dependency> </dependencies> <build> <plugins> <plugin> <groupId>org.springframework.boot</groupId> <artifactId>spring-boot-maven-plugin</artifactId> </plugin> </plugins> </build> </project>
修改application.yml:ide
server: port: 3001 context-path: / spring: application: name: microservice-zuul eureka: instance: instance-id: microservice-zuul:3001 prefer-ip-address: true client: service-url: defaultZone: http://eureka2001.lingerqi.com:2001/eureka/,http://eureka2002.lingerqi.com:2002/eureka/,http://eureka2003.lingerqi.com:2003/eureka/ info: groupId: com.lingerqi.testSpringcloud artifactId: microservice-zuul-3001 version: 1.0-SNAPSHOT userName: http://lingerqi.com phone: 123456
启动类加注解:
@SpringBootApplication(exclude={DataSourceAutoConfiguration.class, HibernateJpaAutoConfiguration.class}) @EnableZuulProxy
测试:
启动三个eureka 而后再启动下一个1001服务,以及 zuul网关服务;
咱们直接请求:http://localhost:1001/student/list 能获取到数据;
咱们用 http://zuul.lingerqi.com:3001/microservice-student/student/list 域名+端口+服务名称+请求地址 也能请求到数据;
说明咱们的路由配置基本OK
上面是zuul的简单使用,从接口地址很轻易的就暴露了服务提供者的惟一标识名microservice-student;有安全风险,咱们须要将其隐藏;
ignored-services的做用是将原来的服务提供者惟一标识名禁用;
Prefix的做用是给服务加前缀
yml文件中添加如下配置:
zuul: routes: studentServer.serviceId: microservice-student studentServer.path: /studentServer/** ignored-services: "*" prefix: /lingerqi
对应的配置会出现下面的错误页面,这是正常现象。
配置完毕后可经过如下连接作测试
http://zuul.lingerqi.com:3001/microservice-student/student/list
http://zuul.lingerqi.com:3001/studentServer/student/list
http://zuul.lingerqi.com:3001/lingerqi/microservice-student/student/list
http://zuul.lingerqi.com:3001/lingerqi/studentServer/student/list
好比咱们登陆某个系统 须要身份验证,用户名密码啥的;
咱们请求服务,也能够来设置身份验证,也就是过滤非法请求;Zuul经过ZuulFilter过滤器实现;
通常具体实现的话 每次通过Zuul服务网关 咱们都对带来的token进行有效性验证;
咱们先定义一个 AccessFilter类:
package com.lingerqi.microservicezuul3001.filter; import com.netflix.zuul.ZuulFilter; import com.netflix.zuul.context.RequestContext; import com.netflix.zuul.exception.ZuulException; import org.apache.log4j.Logger; import javax.servlet.http.HttpServletRequest; /** * @author xyls * @blog name & blog address 027@0030 * @create 2019-12-05 15:40 */ public class AccessFilter extends ZuulFilter { Logger logger=Logger.getLogger(AccessFilter.class); /** * 判断该过滤器是否要被执行 */ @Override public boolean shouldFilter() { return true; } /** * 过滤器的具体执行逻辑 */ @Override public Object run() throws ZuulException { RequestContext ctx = RequestContext.getCurrentContext(); HttpServletRequest request = ctx.getRequest(); String parameter = request.getParameter("accessToken"); logger.info(request.getRequestURL().toString()+" 请求访问"); if(parameter==null){ logger.error("accessToken为空!"); ctx.setSendZuulResponse(false); ctx.setResponseStatusCode(401); ctx.setResponseBody("{\"result\":\"accessToken is empty!\"}"); return null; } // token判断逻辑 logger.info(request.getRequestURL().toString()+" 请求成功"); return null; } /** * 过滤器的类型 这里用pre,表明会再请求被路由以前执行 */ @Override public String filterType() { return "pre"; } /** * 过滤器的执行顺序 */ @Override public int filterOrder() { return 0; } }
而后再开启下 Filter配置:
package com.lingerqi.microservicezuul3001.config; import com.lingerqi.microservicezuul3001.filter.AccessFilter; import org.springframework.context.annotation.Bean; import org.springframework.context.annotation.Configuration; @Configuration public class ZuulConfig { @Bean public AccessFilter accessFilter(){ return new AccessFilter(); } }
Zuul做为服务网关为了保证本身不被服务拖垮,自己已经集成了Hystrix对路由转发进行隔离。 为了方便开发人员对服务短路进行自定义处理,
ZuulFallbackProvider :Zuul 提供了 ZuulFallbackProvider 接口,开发人员能够经过实现该接口来完成自定义Hystrix Fallback
FallbackProvider :Spring Cloud Zuul 提供了 FallbackProvider替代了ZuulFallbackProvider接口。
package com.javaxl.microservicezuul3001.fallback; import org.springframework.cloud.netflix.zuul.filters.route.ZuulFallbackProvider; import org.springframework.http.HttpHeaders; import org.springframework.http.HttpStatus; import org.springframework.http.MediaType; import org.springframework.http.client.ClientHttpResponse; import org.springframework.stereotype.Component; import java.io.ByteArrayInputStream; import java.io.IOException; import java.io.InputStream; @Component public class ZuulFallBack implements ZuulFallbackProvider { @Override public String getRoute() { return "*"; } /** * 在给zuul整合回退功能时,只要类实现ZuulFallbackProvider接口,而且注册bean便可。 * * 不过须要注意的时,这个回退只有服务掉线或者超时的状况下才会触发(Camden.SR4版本测试是这样), * 若是服务程序出现异常,此回退程序是不能处理的,异常会直接返回给调用者,好比页面。 * * @return */ @Override public ClientHttpResponse fallbackResponse() { return new ClientHttpResponse() { @Override public HttpHeaders getHeaders() { HttpHeaders headers = new HttpHeaders(); headers.setContentType(MediaType.APPLICATION_JSON_UTF8);//application/json;charset=UTF-8 return headers; } @Override public InputStream getBody() throws IOException { String msg = "服务繁忙,请稍后....."; //new ByteArrayInputStream("{\"code\":-1,\"msg\":\"服务暂不可用\"}".getBytes(StandardCharsets.UTF_8)) return new ByteArrayInputStream(msg.getBytes()); } @Override public String getStatusText() throws IOException { return HttpStatus.BAD_REQUEST.getReasonPhrase();//400 } @Override public HttpStatus getStatusCode() throws IOException { return HttpStatus.BAD_REQUEST; } @Override public int getRawStatusCode() throws IOException { return HttpStatus.BAD_REQUEST.value();//"Bad Request" } @Override public void close() { } }; } }
浏览器输入地址进行测试
http://zuul.lingerqi.com:3001/lingerqi/studentServer/student/list
http://zuul.lingerqi.com:3001/lingerqi/studentServer/student/list?accessToken=1
测试结果以下: