Timeline for How can I tell when HttpClient has timed out?
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 16, 2021 at 3:01 | comment | added | Simple |
@knocte Check Knelis answer (Feb 1 2021), .NET 5 finally implements a wrapped TimeoutException.
|
|
| Oct 21, 2019 at 11:42 | comment | added | knocte | no I didn't because I can't control HttpClient myself, it's a thirdparty library that I'm using, the one that uses it | |
| Oct 21, 2019 at 8:50 | comment | added | Thomas Levesque |
@knocte, I don't know what to tell you... I've been using this for a long time and it always worked for me. Did you set the HttpClient.Timeout to infinity?
|
|
| Oct 21, 2019 at 2:35 | comment | added | knocte | in the github issue about this, many claim what I said: that IsCancellationRequested is true when there is a timeout; so I'm tempted to downvote your answer ;) | |
| Oct 20, 2019 at 14:17 | comment | added | Thomas Levesque | @knocte that's weird... But in that case, the solution from my blog post won't help you, since it also relies on this | |
| Oct 19, 2019 at 6:26 | comment | added | knocte | ah! it's you! I wrote a comment in your blogpost earlier today. But wrt to this answer, I think your point about IsCancellationRequested is not true, because it seems it's always true for me, when I didn't cancel it myself | |
| Mar 1, 2018 at 16:58 | history | answered | Thomas Levesque | CC BY-SA 3.0 |