Failed to match Route configuration for upstream path using catchAll, everything ...
See original GitHub issueSteps to Reproduce the Problem
- Config the ocelot.json file as follows: ocelot.json
- visit /gateway/Listen route, ocelot fine to route and return data in localhost and docker
- using SignalR Client to visit route, in localhost, it’s fine,
4.but run in docker, same config, thorw follow exception:
requestId: 0HM3VRDIC177A:00000001, previousRequestId: no previous request id, message: Error Code: UnableToFindDownstreamRouteError Message: Failed to match Route configuration for upstream path: /notify/negotiate, verb: POST. errors found in ResponderMiddleware. Setting error response for request path:/notify/negotiate, request method: POST
My Question is, why i set “DownstreamPathTemplate”: “/notify/{catchAll}” and “UpstreamPathTemplate”: “/gateway/notify/{catchAll}”, Ocelot failed to match the route in docker.
Specifications
- Version:16.0.1
- Platform:.net core 3.1 LTS
- Subsystem:windows 10 / docker on centos 7
Issue Analytics
- State:
- Created 3 years ago
- Comments:9 (4 by maintainers)
Top Results From Across the Web
Ocelot Failed to match Route configuration for upstream path
I think you mixed Downstream & Upstream up. Try such config (note values for Host and UpstreamPathTemplate): { "Routes": ...
Read more >Failed to match Route configuration for upstream path ...
My Question is, why i set "DownstreamPathTemplate": "/notify/{catchAll}" and "UpstreamPathTemplate": "/gateway/notify/{catchAll}", Ocelot failed ...
Read more >Routing — Ocelot 1.0.0 documentation
Ocelot's describes the routing of one request to another as a Route. In order to get anything working in Ocelot you need to...
Read more >Ocelot Failed to match Route configuration for upstream path ...
Coding example for the question Ocelot Failed to match Route configuration for upstream path-.net-core.
Read more >Ocelot Documentation
Here is an example Route configuration, You don't need to set all of ... Ocelot tries to match the incoming upstream url with...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Any updates, it wont work on .net 6/7 in my case
I get must be a ws or wss:// url as though its not translating the tranport properly, it tries to connect in gateeway as a http url
@xingwen1987 Hi Richfiter! Are you still with Ocelot in 2023? 😸 We have new release v19.0.2 based on .NET 7