On Thu, Feb 13, 2025 at 9:58 AM Rainer Jung <rainer.j...@kippdata.de> wrote:
> Am 13.02.25 um 09:40 schrieb Cenk Pekyaman: > ... > > > We can reproduce the issue somewhat reliably with the reproducer setup we > > have in https://github.com/cpekyaman/java-server-http2-test. > > The odd part is we could only reproduce it with certain clients reliably, > > with go and curl (we include go client as the failing requests in our > > production systems come from a monitoring system written in go). > > Could you give the curl version as well? I noticed a test failure for > some other web server in the HTTP2 area and learned it was due to some > detail behavior change in curl. In this other situation the failure was > a wrong expectation in the test class. but although you observer > something here in real communication it might still be useful to try > reproducing with the same curl version that you use in case an easy > reproduction attempt does not work. > > Thanks! > > Rainer > > -------------------------------------------------------------------- curl versions: - prod test system 1: 7.76.1 (x86_64-redhat-linux-gnu) libcurl/7.76.1 OpenSSL/3.0.7 zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.1 (+libidn2/2.3.0) libssh/0.10.4/openssl/zlib nghttp2/1.43.0 - prod test system 2: 7.61.1 (x86_64-redhat-linux-gnu) libcurl/7.61.1 OpenSSL/1.1.1k zlib/1.2.11 brotli/1.0.6 libidn2/2.2.0 libpsl/0.20.2 (+libidn2/2.2.0) libssh/0.9.6/openssl/zlib nghttp2/1.33.0 - reproducer (local development machine): 8.7.1 (x86_64-apple-darwin24.0) libcurl/8.7.1 (SecureTransport) LibreSSL/3.3.6 zlib/1.2.12 nghttp2/1.63.0 first two versions are from the systems where our SREs performed initial tests on actual environments, just after the issue was first observed (both were able to reproduce the issue). the last version is from our local development environments.
