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
To achieve hostname verification in CaaS environments, users need to config trustedNames in client.yml and create customized XnioSsl instances. The default Http2Client.SSL does not accept any trustedNames settings.
It turns out that this is not convenient and impacts many client side code. To address this issue, we propose to introduce another config item defaultGroupKey into client.yml.
If defaultGroupKey is configured, the Http2Client.SSL will use the specified key to find trusted names. If this key is not configured, the default HTTPS verification is used.
To achieve hostname verification in CaaS environments, users need to config trustedNames in
client.yml
and create customized XnioSsl instances. The default Http2Client.SSL does not accept any trustedNames settings.It turns out that this is not convenient and impacts many client side code. To address this issue, we propose to introduce another config item
defaultGroupKey
intoclient.yml
.If
defaultGroupKey
is configured, the Http2Client.SSL will use the specified key to find trusted names. If this key is not configured, the default HTTPS verification is used.An example config is shown below:
The text was updated successfully, but these errors were encountered: