http3: SNI should not be set if host is literal IP address #11827

Closed

Closed

http3: SNI should not be set if host is literal IP address#11827

Labels

I did this

curl --http3-only https://1.1.1.1/cdn-cgi/trace

I expected the following

sni=off

curl/libcurl version

curl 8.2.1 (x86_64-w64-mingw32) libcurl/8.2.1 OpenSSL/3.1.2 (Schannel) zlib/1.3 brotli/1.1.0 zstd/1.5.5 WinIDN libssh2/1.11.0 nghttp2/1.56.0 ngtcp2/0.19.1 nghttp3/0.15.0

operating system

windows

ContributorAuthor

https://www.rfc-editor.org/rfc/rfc6066#section-3

Literal IPv4 and IPv6 addresses are not permitted in "HostName".

mentioned this

on Sep 10, 2023

ngtcp2: SNI should not be set if host is literal IP address #11828

added

on Sep 10, 2023

closed this as completedin d5c562c

on Sep 11, 2023

added a commit that references this issue

on Sep 25, 2023

quic: don't set SNI if hostname is an IP address

added a commit that references this issue

quic: don't set SNI if hostname is an IP address

mentioned this

on Mar 21, 2024

H3 deps build script update. apache/trafficserver#11174

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

ngtcp2: SNI should not be set if host is literal IP addresscurl/curl

Participants