You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Which works perfectly, but I have a requirement where the UpstreamPathTemplate is "/Users/$metadata"
I observed that if the UpstreamPathTemplate has a dollar ($) then we get an error -
Ocelot.Responder.Middleware.ResponderMiddleware:Warning: requestId: 800000b2-0003-f500-b63f-84710c7967bb, previousRequestId: no previous request id, message: Error Code: UnableToFindDownstreamRouteError Message: Failed to match ReRoute configuration for upstream path: /Users/$metadata, verb: GET. errors found in ResponderMiddleware. Setting error response for request path:/Users/$metadata, request method: GET
The text was updated successfully, but these errors were encountered:
how did you manage to solve this? I had the same problem. You would declare the UpstreamPathTemplate like "/\$metadata", like you where escaping the $ character. The reason for this is I think is because internally Ocelota uses regex and $ gets interpreted different
I am also working with Ocelot and OData and trying to create an aggregated /$metadata endpoint in ocelot. There are a few problems to solve and I have just come across this one. Would love to know if there is a work around?
I have this configuration in ReRoutes -
Which works perfectly, but I have a requirement where the UpstreamPathTemplate is "/Users/$metadata"
I observed that if the UpstreamPathTemplate has a dollar ($) then we get an error -
Ocelot.Responder.Middleware.ResponderMiddleware:Warning: requestId: 800000b2-0003-f500-b63f-84710c7967bb, previousRequestId: no previous request id, message: Error Code: UnableToFindDownstreamRouteError Message: Failed to match ReRoute configuration for upstream path: /Users/$metadata, verb: GET. errors found in ResponderMiddleware. Setting error response for request path:/Users/$metadata, request method: GET
The text was updated successfully, but these errors were encountered: