HTTP/3 Extension Order Issue in H3 Connections

[alpgul]

https://github.com/lexiforest/curl-chrome/blob/7b5f3b36d0e120c26e01c5df3c75a0a3478c1e3f/lib/vtls/openssl.c#L4697-L4700

    char *ext_order = (peer->transport == TRNSPRT_QUIC
                       && data->set.str[STRING_HTTP3_TLS_EXTENSION_ORDER])
                      ? data->set.str[STRING_HTTP3_TLS_EXTENSION_ORDER]
                      : data->set.str[STRING_TLS_EXTENSION_ORDER];

When the HTTP/3 extension order value is defined as null, the system incorrectly uses the H2 extension order settings for H3 connections.
The following part of the code should be removed: && data->set.str[STRING_HTTP3_TLS_EXTENSION_ORDER]

[lexiforest]

When the HTTP/3 extension order value is defined as null, the system incorrectly uses the H2 extension order settings for H3 connections.

Why shouldn't this be the expected behavior?

[alpgul]

If the HTTP/3 connection does not have an ordering defined and the HTTP/2 connection does, the HTTP/3 connection will be forced to use the ordering belonging to HTTP/2.

[lexiforest]

I would consider this an undefined behavior that won't be fixed. If you are impersonating, you should set this option, if you are not, the value of this option is irrelevant anyway.