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
In routes i have "UpstreamPathTemplate": "/starwars/{everything}",
By this configuration I only get error that
Failed to match Route configuration for upstream path: /swagger/docs/v1/starwars
Which is true because I didn't know that i need to define extra route
So after adding another rote configuration "UpstreamPathTemplate": "/swagger/docs/v1/starwars",
It was working fine.
Expected behavior
Dont really know why swagger routes generated by this library are opposed instead starwars/swagger/docs/v1/ what is generated is /swagger/docs/v1/starwars
I assume reason is that my swagger endpoint is not as in documentation domain/swagger but domain/api/swagger
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Describe the bug
Im using KubernetesServiceDiscoveryProvider ,
I defined swagger endpoint
In routes i have
"UpstreamPathTemplate": "/starwars/{everything}",
By this configuration I only get error that
Failed to match Route configuration for upstream path: /swagger/docs/v1/starwars
Which is true because I didn't know that i need to define extra route
So after adding another rote configuration
"UpstreamPathTemplate": "/swagger/docs/v1/starwars",
It was working fine.
Expected behavior
Dont really know why swagger routes generated by this library are opposed instead starwars/swagger/docs/v1/ what is generated is /swagger/docs/v1/starwars
I assume reason is that my swagger endpoint is not as in documentation domain/swagger but domain/api/swagger
Config file
The text was updated successfully, but these errors were encountered: