Am 09.03.23 um 11:29 schrieb Stefan Eissing via dev:
Am 09.03.2023 um 11:22 schrieb Rainer Jung :
Puzzle partially solved: once I add "--header 'content-type:
application/x-www-form-urlencoded'" to the nghttp call, the problem seems fixed -
with and without deflate. No more hang, no more
> Am 09.03.2023 um 11:22 schrieb Rainer Jung :
>
> Puzzle partially solved: once I add "--header 'content-type:
> application/x-www-form-urlencoded'" to the nghttp call, the problem seems
> fixed - with and without deflate. No more hang, no more status 500, no double
> requests. I still
Puzzle partially solved: once I add "--header 'content-type:
application/x-www-form-urlencoded'" to the nghttp call, the problem
seems fixed - with and without deflate. No more hang, no more status
500, no double requests. I still don't know, which side is influenced,
nghttp or http, so I am
OK, I can test in a standalone situation now.
The problem goes away, once I use curl, even with h2.
The problem also goes away, once I disable deflate compression for the
response. But curl and nghttp behave different: nghttp hangs after
receiving the response body (no deflate), curl normally
I will see how to extract the test case out of pytest to be able to run
it standalone and vary the protocol. But the connection reset plus
second request might also be nghttp specific. I will also try running
nghttp from remote and sniff to double check the connection reset plus
second
Thanks for the tip. I already did the "run only one test case" and I
fixed the LogLevel in test.conf to include trace8. So I guess there will
not be any additional CGI logging available. But good to know the "-vvv".
Thanks and regards,
Rainer
Am 09.03.23 um 09:33 schrieb Stefan Eissing via
One tip, if you call "pytest -vvv -k test_h2_202_03b", it will run just that
test and raise LogLevel for several "interesting" modules.
The error log in test/gen/apache/logs/error_log will then show just that one
test case. It's a convenient way to get more information without meddling with
On 3/8/23 10:44 PM, Rainer Jung wrote:
> Hi there,
>
> I currently get three consistent pytest failures:
Do A) and B) work if you do the requests via HTTP/1.1?
Regards
Rüdiger
