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
Attempting to make a self-signed HttpServer and HttpClient dialog through SSL, this leads to unstable state and the server will loop forever, never managing to negotiate the SSL handshake.
At the root cause is HttpClientOptions.formatSchemeAndHost, which doesn't use the HTTPS (or WSS) scheme even though the SslContext is set.
The text was updated successfully, but these errors were encountered:
This commit fixes HttpClient not correctly working with SSL activated
when performing a request (eg. get) on a relative url/path.
This was due to HttpClientOptions.formatSchemeAndHostRelative not taking
the SslContext configuration into account when creating a full URL for
such a request, resulting in HTTP requests being performed on a HTTPS
connection.
This commit fixes HttpClient not correctly working with SSL activated
when performing a request (eg. get) on a relative url/path.
This was due to HttpClientOptions.formatSchemeAndHostRelative not taking
the SslContext configuration into account when creating a full URL for
such a request, resulting in HTTP requests being performed on a HTTPS
connection.
Attempting to make a self-signed
HttpServer
andHttpClient
dialog through SSL, this leads to unstable state and the server will loop forever, never managing to negotiate the SSL handshake.At the root cause is
HttpClientOptions.formatSchemeAndHost
, which doesn't use theHTTPS
(orWSS
) scheme even though theSslContext
is set.The text was updated successfully, but these errors were encountered: