简体   繁体   English

生产中的 Zuul 网关

[英]Zuul gateway at production

I'm migrating my application to micro-services and also implementing zuul+eureka for gateway and service registry.我正在将我的应用程序迁移到微服务,并为网关和服务注册表实现 zuul+eureka。 Everything works fine at local.在本地一切正常。 (Able to access backend service using zuul). (能够使用 zuul 访问后端服务)。

When i'm deploying this configuration at server level for single instance of each client or multiple instance of a client at same server (zuul and client) working fine.当我在服务器级别为每个客户端的单个实例或同一服务器(zuul 和客户端)上的多个客户端实例部署此配置时,工作正常。 What shall i do in order to access a client service running on different server (Not localhost) using zuul url ?.我应该怎么做才能使用 zuul url 访问在不同服务器(不是本地主机)上运行的客户端服务? (As far as i understood till now that zuul used to route internal backend service). (据我所知,zuul 用于路由内部后端服务)。

Hi, I have this configuration in the .yml嗨,我在 .yml 中有这个配置

zuul: 
  debug: 
    request: true 
    add-proxy-headers: false 
  routes: ServiceName
  path: /pathMyService/** 
  url: https://www0.app.appcorp.es/widgets/register/pub/bff/baselegal/getBases

So, when from my localhost I call http: //localhost:8002/pathMyService/ internally netflix-zuul is redirecting to the property url ( https://www0.app.appcorp.es/widgets/register/pub/bff/baselegal/getBases )因此,当从我的本地主机调用 http://localhost:8002/pathMyService/ 在内部 netflix-zuul 重定向到属性 url ( https://www0.app.appcorp.es/widgets/register/pub/bff/baselegal /getBases )

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM