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

net/http: how to distinguish connection timeout or response timeout #29489

Closed
wrztye opened this issue Jan 1, 2019 · 3 comments
Closed

net/http: how to distinguish connection timeout or response timeout #29489

wrztye opened this issue Jan 1, 2019 · 3 comments

Comments

@wrztye
Copy link

wrztye commented Jan 1, 2019

net/http/client: how to distinguish connection timeout or response timeout

@tomor
Copy link

tomor commented Jan 1, 2019

Can you describe more broadly the problem you are trying to solve?
Why do you need to distinguish connection timeout from response timeout?

@wrztye
Copy link
Author

wrztye commented Jan 2, 2019

I'm working on an RPC framework.
If the connection timeouts, I can try again.
If the response timeouts, I can't retry. Because the request may have been sent.

@dmitshur dmitshur changed the title net/http/client: how to distinguish connection timeout or response timeout net/http: how to distinguish connection timeout or response timeout Jan 6, 2019
@andybons
Copy link
Member

Hi there,
We have decided that our experiment to allow questions on the issue tracker has not had the outcome we desired, so I am closing this issue. I'm sorry that we can't answer your question here.

There are many other methods to get help if you're still curious:

Thanks

@golang golang locked and limited conversation to collaborators Aug 11, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

5 participants