-
|
According to netty/netty#9930 and netty/netty#8537, TLS hostname verification is not enabled by default in native Netty. It seems that the AWS Java SDK has fixed this issue internally here: https://github.com/aws/aws-sdk-java-v2/pull/1184/files#diff-0a4c5b5016e0d0df7ff524caf127245455248ce52c393853cec0a40c95a8f5a1R103-R116. But I don't know the codebase well enough to connect the above code with the user-facing Can someone please confirm / deny whether hostname verification is fixed in AWS' Netty-based HTTP client? Thanks! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
Yes, we have hostname verification enabled in NettyNioAsyncHttpClient. |
Beta Was this translation helpful? Give feedback.
-
|
Awesome, thanks a lot! |
Beta Was this translation helpful? Give feedback.
-
|
Hello! Reopening this discussion to make it searchable. |
Beta Was this translation helpful? Give feedback.
Yes, we have hostname verification enabled in NettyNioAsyncHttpClient.