-
Notifications
You must be signed in to change notification settings - Fork 29
Host/Headers not always sent with 1.10.1 #44
Comments
Thanks for reporting the issue. But sorry that no one can do anything, until you provide the complete MRE so that we can duplicate the issue. Please do more tests to prove this is actually a bug of the library or just in your use-case (code / server, etc.) BR, |
Hi @khoih-prog In this sample the call is performed at every 5 seconds. Every second call returns in a 400 bad request error (hostname header is missing). If I change the intervall to 10 seconds, the issue won't appear, as it will always open a new connection.
That is what apache complains about: Hope that helps. |
Sorry I couldn't duplicate the issue using the example with 5s request interval, even with more complex site, Check the debug terminal with timestamps.
Possibly something wrong ( not compatible / slow network , etc.) of your Good Luck, Terminal
|
Anyway, I'll create and release a new version to default to resend headers, etc. after already connected, to avoid error with new Apache Webserver The test is OK with 5s between request now, w/o
|
### Releases v1.10.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](https://github.com/khoih-prog/AsyncHTTPRequest_Generic/issues44) 2. Update `Packages' Patches`
### Releases v1.10.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](https://github.com/khoih-prog/AsyncHTTPRequest_Generic/issues44) 2. Use `allman astyle` with utils 3. Update `Packages' Patches`
The new AsyncHTTPRequest_Generic v1.10.2 has just been published. Your contribution is noted in Contributions and Thanks Please test and report more bugs. Best Regards, Releases v1.10.2
|
### Releases v2.2.1 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) and [Getting 400 Bad Request on second call to same host #14](#14) 2. Use `allman astyle` and add `utils`
### Releases v2.2.1 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) and [Getting 400 Bad Request on second call to same host #14](#14) 2. Use `allman astyle` and add `utils`
### Release v1.2.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Fix bug 3. Use `allman astyle` and add `utils`
### Release v1.2.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Fix bug 3. Use `allman astyle` and add `utils`
### Release v1.9.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Use `allman astyle` and add `utils`
### Release v1.9.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Use `allman astyle` and add `utils`
### Releases v1.4.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Use `allman astyle` and add `utils`
### Releases v1.4.2 1. Default to reconnect to the same `host:port` after connected for new HTTP sites. Check [Host/Headers not always sent with 1.10.1 #44](khoih-prog/AsyncHTTPRequest_Generic#44) 2. Use `allman astyle` and add `utils`
Many many thanks! I can confirm it's working fine. |
Hi
today I updated your library to 1.10.1 and now I spot an issue:
every second call seems to miss header informations, my server returns back:
<h1>Bad Message 400</h1><pre>reason: No Host</pre>
User @dirkvranckaert was already mentioning the same on issue #43, but I can't see if he was having that issue with 1.10.1 or 1.9.1. I did not have the issue with 1.9.1 (but the buggy callback behaviour instead).
#43 (comment)
Unfortunately I struggle to enable debugging, possibly it can be reproduced with the example provided with #43.
I use an ESP32 and the endpoint is an IP-address (no DNS), just in case that might matter. If you need more details, please let me know.
The text was updated successfully, but these errors were encountered: