HTTP/2 + connection pool settings in confighttp: what is the intended behavior?

[dsevr]

I’m trying to understand the intended contract around ForceAttemptHTTP2 in confighttp.ClientConfig.

As I read the code today:

• ForceAttemptHTTP2 defaults to true
• MaxConnsPerHost, MaxIdleConnsPerHost, and MaxIdleConns are documented as unsupported under HTTP/2
• These fields are still accepted in config but have no effect when HTTP/2 is used
• There’s no runtime warning or validation when these options are set together

Is my understanding of the current behavior correct, and is it intended to be doc-only, or should users expect some runtime signal when HTTP/2 is enabled and these options are set?

Code references

• Default HTTP/2 enabled: config/confighttp/client.go:L126–L134
• Documented incompatibility: config/confighttp/client.go:L106–L108
• No validation/warning: config/confighttp/client.go:L137–L144

Thanks.