Closed CorrectRoadH closed 7 months ago
Understood your needs, however, we need to consider the issue of parameter passing, such as the passing of the 'best', 'randomName', and 'key' parameters.
Understood your needs, however, we need to consider the issue of parameter passing, such as the passing of the 'best', 'randomName', and 'key' parameters.
Ok. I will try to resolve the problem of the consistency of managed url.
What does the PR do?
add a environment var to custom the surge managed url.
In general, the surge managed url is
http://yourIP:21001/api/surge
. But in some cases. We need add a reverse proxy in front of WARP clash API. the url may likehttps://sub.xxxx.xxx
orhttps://sub.xxxx.xxx/surge
.So in the point view of product and user. I had to join the feature to WARP Clash API. Although it add some complexity.