binary post timeout #116
Comments
|
OK. Let's try to understand what is happening. What I understand so far from your report:
Immediately, I tried to reproduce your scenario using a demo HTTP/3 server and it worked without error. To dig this further, we need to know:
On your side, try: A) Try to add B) Try to replace C) Run your code, the original one, but add this code to be executed before all: import logging
logger = logging.getLogger()
logger.setLevel(logging.DEBUG)
explain_handler = logging.StreamHandler()
explain_handler.setFormatter(
logging.Formatter("%(asctime)s | %(levelname)s | %(message)s")
)
logger.addHandler(explain_handler)And copy/paste the logs here. Regards, |
|
Without further information, it will be impossible for me to investigate.
If the issue persist, let us know. |
|
Sorry .. other work sidetracked me for a couple of days. We terminate http/2 and http/3 in traefik 2.11 A. disable_http3 worked correctly |
…ed key derivation Close jawah/niquests#116
…ed key derivation (#33) Close jawah/niquests#116
|
No worries about it. So! I managed to reproduce the error. This is good news. It seems that <=v2.10.4 (and others for that matter) have a weak spot. it did not rotate the key... often enough...? so our test suite was weak on that point. We fixed the issue in the latest qh3 version. Run Thank you for the detailed report. Regards, |
|
Thanks.. I wanted to confirm that the patch fixed the issue I saw.
I will continue to test with our other services.
Thanks for the cool package.
Kris
…On Tue, May 7, 2024 at 10:21 PM TAHRI Ahmed R. ***@***.***> wrote:
No worries about it.
So! I managed to reproduce the error. This is good news.
The weird thing is.. we use Traefik for our integration pipeline and did
not notice that error prior to your discovery.
Well, we used Traefik v2.10.4 and this error occurred since v2.10.5 or
newer.
It seems that <=v2.10.4 (and others for that matter) have a weak spot. it
did not rotate the key... often enough... so our test suite was weak on
that point.
We fixed the issue in the latest qh3 version. Run pip install qh3 -U
v1.0.7 to fix this definitely. The release process may take up to one hour
(starting now).
Thank you for the detailed report.
Regards,
—
Reply to this email directly, view it on GitHub
<#116 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AANVHIGXTXK5APS2MVHRHO3ZBGY6ZAVCNFSM6AAAAABHBCWBD2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAOJZG43DEMRSGI>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
--
Kristian G. Kvilekval ***@***.***) 805-636-1599
|
|
Your feedback are most welcome. regards, |
a post of a binary fails to connect
Expected Result
When run with requests :
Actual Result
When using niquests
Reproduction Steps
System Information
Failed 1st time because h2 was missing after executing pip install h2 I get
{ "charset_normalizer": { "version": "3.3.2" }, "http1": { "h11": "0.14.0" }, "http2": { "h2": "4.1.0" }, "http3": { "enabled": true, "qh3": "1.0.4" }, "idna": { "version": "3.7" }, "implementation": { "name": "CPython", "version": "3.11.2" }, "niquests": { "version": "3.6.1" }, "ocsp": { "enabled": true }, "platform": { "release": "6.1.0-18-amd64", "system": "Linux" }, "system_ssl": { "version": "300000b0" }, "urllib3.future": { "cohabitation_version": null, "version": "2.7.905" }, "wassima": { "certifi_fallback": false, "enabled": true, "version": "1.1.1" } }The environmen allow me to use niquest against the server
The text was updated successfully, but these errors were encountered: