Skip to content
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

I want to support the API to add multiple [request paths: /*]. The apinto V1 version is supported. #120

Open
ezjbc opened this issue Jul 9, 2023 · 4 comments

Comments

@ezjbc
Copy link

ezjbc commented Jul 9, 2023

Description

I want to support the API to add multiple [request paths: /]. The apinto V1 version is supported.
image
Previously, I used to request the path: /
, and forward upstream through the parameters in the header

@Dot-Liu
Copy link
Collaborator

Dot-Liu commented Jul 14, 2023

收到您的反馈,这里涉及到了接口重复校验的算法,我们研究一下怎么处理

@Dot-Liu
Copy link
Collaborator

Dot-Liu commented Aug 9, 2023

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.

@Mr-TianLang
Copy link

请问咱们有实现这个功能的计划没,灰度发布的必须写死节点地址,不太满足业务需求

@Dot-Liu
Copy link
Collaborator

Dot-Liu commented Feb 5, 2024

已经支持了,更新到最新版本的控制台即可

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants