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

fetch2 timeout too long / not working #874

Closed
ldemailly opened this issue Dec 15, 2023 · 2 comments · Fixed by #875
Closed

fetch2 timeout too long / not working #874

ldemailly opened this issue Dec 15, 2023 · 2 comments · Fixed by #875

Comments

@ldemailly
Copy link
Member

When the host/ip isn't reachable it seems it hangs indefinitely or at least for a very long time

@ldemailly
Copy link
Member Author

On mac, added to /etc/pf.conf

block drop out proto tcp from any to 18.222.136.83 port 443

and

sudo pfctl -f /etc/pf.conf

So the first address for https://debug.fortio.org/ is blocked

Updated #616 as noticed that the std client which is now the default in the UI gets stuck on first IP even with 3 or 6 connections - but does have a timeout, so does fortio curl is also timing out as expected (unless using -dns-method rnd then it timesout 1/3rd of the time when using that blocked ip/port)

And indeed fetch2 handler blocks until you navigate away and only then one gets

13:20:28.592 r41 [ERR] http_server.go:541> Error for "https://debug.fortio.org/": Get "https://debug.fortio.org/": context canceled

@ldemailly
Copy link
Member Author

went back to go 1.19 and fortio 1.40.1 and same behavior, so not a regression but never handled hanging connection in proxy

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

Successfully merging a pull request may close this issue.

1 participant