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.

Sign up for GitHub

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

Jump to bottom

net/http: easier way to check whether an error is due to timeout #6185

Closed
gpaul opened this issue Aug 19, 2013 · 7 comments
Closed

net/http: easier way to check whether an error is due to timeout #6185

gpaul opened this issue Aug 19, 2013 · 7 comments
Labels
FrozenDueToAge
Milestone
Go1.3

Comments

@gpaul
Copy link
Contributor

gpaul commented Aug 19, 2013 

Currently the only way to check whether a Get/Post/Do failed due to the respond headers
taking too long is to check the error string for the proper contents.

It would help if http.responseAndError satisfied the net.Error interface so one could
check for err.Timeout() if you'd like to treat timeouts differently.

go version: 1.1.1
@robpike
Copy link
Contributor

robpike commented Aug 19, 2013

Comment 1:

Labels changed: added priority-later, removed priority-triage.

Status changed to Accepted.

@rsc
Copy link
Contributor

rsc commented Sep 10, 2013

Comment 2:

Labels changed: added go1.3, removed go1.2maybe.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 3:

Labels changed: added release-go1.3.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 4:

Labels changed: removed go1.3.

@rsc
Copy link
Contributor

rsc commented Dec 4, 2013

Comment 5:

Labels changed: added repo-main.

@gopherbot
Copy link

Comment 6 by rickarnoldjr:

https://golang.org/cl/55470048/

@bradfitz
Copy link
Contributor

Comment 7:

This issue was closed by revision 5e711b4.

Status changed to Fixed.

@rsc rsc added this to the Go1.3 milestone Apr 14, 2015
@rsc rsc removed the release-go1.3 label Apr 14, 2015
@golang golang locked and limited conversation to collaborators Jun 24, 2016
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
FrozenDueToAge
Projects
None yet
Milestone
Go1.3
Development

No branches or pull requests
5 participants
@gpaul @bradfitz @rsc @robpike @gopherbot