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
I want to support the API to add multiple [request paths: /]. The apinto V1 version is supported.
Previously, I used to request the path: /, and forward upstream through the parameters in the header
The text was updated successfully, but these errors were encountered:
Hello, after discussion, for an API, the routing characteristics are composed of the request path, request method, and request domain name
Generally, there is no situation where the path is the same, the request parameters (Header or Query) are different, and the upstream services pointed to are different
If there is such a requirement, it is usually related to upgrading, and version numbers are distinguished through parameters to forward to different upstream services
At this point, we suggest that you use a grayscale publishing strategy. We will optimize the problem of duplicate configuration combinations of request path, request method, and request domain name
By requesting parameters to point to different upstream services, we are currently not compatible. Thank you for your feedback.
Description
I want to support the API to add multiple [request paths: /]. The apinto V1 version is supported.
![image](https://private-user-images.githubusercontent.com/51684966/252127337-5c726987-0f5a-4adf-8710-57def7ff0972.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTk5MjIwMDgsIm5iZiI6MTcxOTkyMTcwOCwicGF0aCI6Ii81MTY4NDk2Ni8yNTIxMjczMzctNWM3MjY5ODctMGY1YS00YWRmLTg3MTAtNTdkZWY3ZmYwOTcyLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA3MDIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwNzAyVDEyMDE0OFomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTI5ZDg2NGQ2MjZlNDQxNWZiZjZlOGVmMjcwOTU1NThhMGIwZGE2MzYxYzVlZmVjZjAzMDM0MTcxMTAyNzQzYjAmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.QvDnuiBw05Sa_4Ls51GRUQbwZan5luG0PvkotpxdWLs)
Previously, I used to request the path: /, and forward upstream through the parameters in the header
The text was updated successfully, but these errors were encountered: