-
-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
[FET] add lazy option to endpoints #2682
Comments
I am not very sure if this behavior should be regard as a If not The solution without reviewing code is very naive and just trigger the |
You misunderstood. This Please submit the original bug instead of speculating on the cause. |
So you prefer to regard it as the bug? How do you explain the behavior, once we trigger one success of connection to endpoint, then it work normal without long term delay? |
However, while changing |
Operating system
macOS
System version
15.3.1
Installation type
sing-box for macOS Graphical Client
If you are using a graphical client, please provide the version of the client.
1.11.4
Version
Description
When have
endpoints
in client side, it will not start instantly but wait for the incoming request, which leads a long time wait (~60s) on web browser, especially when connect to warp network.In practice, when start the sing-box app. If we directly access
reddit.com
, which defined as should route viaWARP
here in givenconfig.json
, it cost60s
to finally load in web page. However, if we executecurl -fsSL https://ipinfo.io/ip
, before accessreddit.com
, it cost only 3 seconds, due tocurl -fsSL https://ipinfo.io/ip
trigger theendpoints
started.Reproduction
config.json
Logs
Supporter
Integrity requirements
The text was updated successfully, but these errors were encountered: