-
Notifications
You must be signed in to change notification settings - Fork 29
setTimeout() hasn't any effect #38
Comments
### Releases v1.9.0 1. Fix long timeout if using `IPAddress`. Check [setTimeout() hasn't any effect #38](#38) 2. Optimize code 3. Display only successful responseText in examples 4. Improve debug messages by adding functions to display error messages instead of `cryptic error number` 5. Remove support to STM32 using **LAN8720** due to problem with new STM32 core v2.3.0 5. Update `Packages' Patches`
### Releases v1.9.0 1. Fix long timeout if using `IPAddress`. Check [setTimeout() hasn't any effect #38](#38) 2. Optimize code 3. Display only successful responseText in examples 4. Improve debug messages by adding functions to display error messages instead of `cryptic error number` 5. Remove support to STM32 using **LAN8720** due to problem with new STM32 core v2.3.0 5. Update `Packages' Patches`
Hi @miwied The new AsyncHTTPRequest_Generic releases v1.9.0 has just been published. Your contribution is noted in Contributions and Thanks Best Regards, Releases v1.9.0
Use the following code to test the new library version Test Code
Using correct hostname
|
Hi @khoih-prog, first of all I would like to thank you for addressing the problem so quickly and looking for a possible solution. I now tested the new library for about one hour and unfortunately, I have to tell you that the results are different for me than for you and the problem still exists. 😕 Here is the code I used (your test code):
Here are the results:1.) Using correct hostname 2.) Using bad IP Address
3.) Using bad hostname
Look closely on the timestamps in both logs. If requesting the bad ip address the lines
are delayed by 18 seconds... this does not occur when requesting the bad hostname. Do you have an idea why this is happening? |
Please read previous answer Using bad IPAddress
|
@khoih-prog Ok. In my case the |
Describe the bug
If address is a normal address e.g.:
http://exampleasynchttp.com/index.html
, it gives immediately a "-4" code if not available (good).But if the address is a ip address like
http://192.168.0.44/index.html
(this host is down) the timeout takes always about 18 seconds no matter how many seconds you set (not good).Steps to Reproduce
Copy code from:
https://gist.github.com/miwied/f56aca82c4f976f448dde1a8da051650
Flash it to esp32 and run.
Expected behavior
The request should time out after 3 seconds.
Actual behavior
The request is always timing out after 18 seconds (no matter what you pass into the setTimeout() method).
Additional Information
The
_onPoll(AsyncClient *client)
method, where the timeout is queried, is never called.The text was updated successfully, but these errors were encountered: