-
Notifications
You must be signed in to change notification settings - Fork 1.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
use ocelot in docker can't route to raw service #934
Comments
I also have this problem. But, why is it designed like this? |
Leandropintogit
pushed a commit
to Leandropintogit/Ocelot
that referenced
this issue
Oct 29, 2019
Leandropintogit
pushed a commit
to Leandropintogit/Ocelot
that referenced
this issue
Oct 29, 2019
Fixed by #909 Current code: Ocelot/src/Ocelot.Provider.Consul/Consul.cs Lines 59 to 61 in f4803c2
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior / New Feature
change Ocelot.Provider.Consul.Consul Line 60:
// new ServiceHostAndPort(serviceNode == null ? serviceEntry.Service.Address : serviceNode.Name, serviceEntry.Service.Port),
new ServiceHostAndPort(serviceEntry.Service.Address, serviceEntry.Service.Port),
Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware:Debug: requestId: 0HLNKD0PKJCRA:00000002, previousRequestId: no previous request id, message: Downstream url is http://192.168.1.50:5002/common/v1/swagger.json
Actual Behavior / Motivation for New Feature
Ocelot.DownstreamUrlCreator.Middleware.DownstreamUrlCreatorMiddleware:Debug: requestId: 0HLNKD0PKJCRA:00000002, previousRequestId: no previous request id, message: Downstream url is http://devserver:5002/common/v1/swagger.json
No Such Device or Address Error.
Steps to Reproduce the Problem
Specifications
The text was updated successfully, but these errors were encountered: