--host has no effect when used in combination with --http2

[gerhard]

In the context of thechangelog/pipely#46, I came across the following issue in oha 1.12.1

oha -n 10 --no-tui --http2 --host cdn.changelog.com https://changelog.com/
# ...
Status code distribution:
  [421] 10 responses ❌ RESPONSE STATUS SHOULD BE 404

Without the --http2 flag, it works as expected:

oha -n 10 --no-tui --host cdn.changelog.com https://changelog.com/
# ...
Status code distribution:
  [404] 10 responses ✅ STATUS CODE IS 404, AS EXPECTED

The above makes me suspect that --host flag has no effect when used in combination with the --http2 flag.

As a workaround, I changed all benchmarks to use HTTP 1.1.

Big fan of hey @hatoo , thank you for building such an awesome TUI-based HTTP bench tool 🙏

---

Related to:

• incorrect header host value? #308

[hatoo]

Hi, you are right, --host has not effect with --http2 because host header must not be present on http/2 according to https://datatracker.ietf.org/doc/html/rfc9113#section-8.3.1

Clients MUST NOT generate a request with a Host header field that differs from the ":authority" pseudo-header field. A server SHOULD treat a request as malformed if it contains a Host header field that identifies an entity that differs from the entity in the ":authority" pseudo-header field.

You can simply target to https://cdn.changelog.com/ or use --connect-to option

 --connect-to <CONNECT_TO>
          Override DNS resolution and default port numbers with strings like 'example.org:443:localhost:8443'
          Note: if used several times for the same host:port:target_host:target_port, a random choice is made

[gerhard]

Makes sense! Works as expected, closing this now. Thank you @hatoo for a most helpful reply.