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
Since the changes in applied ca29e56, the default SSL configuration does not work without the boringssl dependency on classpath.
I'm not sure I understand the logic behind the latest changes with SSL/H2 support in reactor-netty.
It seems that we can now configure the supported protocols on the server itself, whereas the SSL configuration also has an impact on that support. This can lead to strange situations.
HTTP 1.1 with SSL, no boringSSL dependency
Without the tcnative dependency on classpath, and the following server:
Since the changes in applied ca29e56, the default SSL configuration does not work without the boringssl dependency on classpath.
I'm not sure I understand the logic behind the latest changes with SSL/H2 support in reactor-netty.
It seems that we can now configure the supported protocols on the server itself, whereas the SSL configuration also has an impact on that support. This can lead to strange situations.
HTTP 1.1 with SSL, no boringSSL dependency
Without the tcnative dependency on classpath, and the following server:
Trying to send a request to the server:
This breaks with the following:
HTTP 1.1 with SSL, with tcnative/boringSSL dependency
When I do add the tcnative dependency to the classpath and try using SSL+HTTP1.1, it's still failing with the following:
On the client side, it seems client and server are trying to use H2 anyway:
HTTP 1.1 with SSL, no tcnative/boringSSL dependency, fixed
If I then override completely the default configuration, this works:
The text was updated successfully, but these errors were encountered: