-
Notifications
You must be signed in to change notification settings - Fork 13.3k
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
Timeout set using Client::setTimeout is not taken into account in WiFiClient::connect #2120
Comments
Hi,Hallard |
I'm curious about the status of this? Particularly, I'm wanting to know what the default timeout is when using the WiFiClient client; / client.connect() call? And if I know the default, can I change this? Likewise (slightly off topic) what is the default timeout on ESPhttpUpdate.update()? And is this also settable? |
for reliable performance or periodic remote HTTPClient request , I think HTTPClient should be rewritten in async mode, because sync stack has no correct idea about status of remote server and if you run the websocket server probably it will be failed |
Will track this in #1420. |
Hardware
Hardware: nodemcu ESP12
Core Version: latest git
Description
I think I misunderstood something, with HTTPClient library, I'm calling
http.setTimeout(1000);
it works once connected to server and when doing ahttp.get()
. No pb at allBut whatever value I use if the server is down or not responding
http.begin()
seems to default to 5 secondsSettings in IDE
Module: NodeMCU V1.0
Flash Size: 4MB/1MB
CPU Frequency: 160Mhz
Flash Mode: qio
Flash Frequency: 40Mhz
Upload Using: OTA
Reset Method: nodemcu
Sketch
Here my function
Debug Messages
Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.
The text was updated successfully, but these errors were encountered: