HTTP/3 works, but testing tools say no?

Help
1

1. The problem I’m having:

I see the interesting effect that a lot of accesses (including curl3) to my configured sites use the HTTP/3 protocol fine, but when I am using the testing tools Check HTTP Protocol of any domain - Siterelic I see that they think HTTP/3 is not supported. But they do not describe what they use to find that out. I looked in my log an I see requests from them using HTTP/1.1 and then HTTP/2.0 but no HTTP/3.0. An example is https://amun.mager.org, when accessed in Chrome I see HTTP/3.0, but using Siterelic I see that HTTP/3.0 is not supported.

2. Error messages and/or full log output:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

3. Caddy version:

4. How I installed and ran Caddy:

a. System environment:

b. Command:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

c. Service/unit/compose file:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

d. My complete Caddy config:

PASTE OVER THIS, BETWEEN THE ``` LINES.
Please use the preview pane to ensure it looks nice.

5. Links to relevant resources:

2

I mean, we can’t help you with those kinds of testing tools. What they do under the hood is a mystery to us. They might be checking the wrong QUIC version in the protocol (checking for old/deprecated versions) and don’t recognize the latest protocol specs. You’d have to reach out to those testing tool authors.

Just use open source, well-known and understood tools for your testing, instead of random websites like this. Curl with HTTP/3 support is a great way to test it.

1 Like