You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Invalid HTTP/2 origin set when servername is empty #39919
(node:36333) [DEP0123] DeprecationWarning: Setting the TLS ServerName to an IP address is not permitted by RFC 6066. This will be ignored in a future version.
(Use `node --trace-deprecation ...` to show where the warning was created)
[ 'https://1.1.1.1' ]
@szmarczak
According to the additional information you have provided, this is the intended behaviour, the server name is supposed to be a valid domain name in the SSL certificate. Using IP addresses in the SSL certificate is not encouraged.
However, this is just an additional information. The original bug remains a bug. Maybe somewhere the empty servername property is being substituted without checking its value, which is resulting in https://false. Weird haha.
Activity
Narasimha1997 commentedon Aug 29, 2021
@szmarczak
According to the additional information you have provided, this is the intended behaviour, the server name is supposed to be a valid domain name in the SSL certificate. Using IP addresses in the SSL certificate is not encouraged.
However, this is just an additional information. The original bug remains a bug. Maybe somewhere the empty
servernameproperty is being substituted without checking its value, which is resulting inhttps://false. Weird haha.Narasimha1997 commentedon Aug 29, 2021
#39934 seems to fix this bug.
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty
http2: set origin name correctly when servername is empty