Ok, I figured it out. As I can't use insecure WebSocket inside the WKWebView if I am in HTTPS (what I want), the best option is to get rid completely of the WebSocket server and to use WKScriptMessage instead which allows to send JavaScript to native code in a WKWebView. Furthermore, we get rid of networking issues we can have with the WebSocket server and since iOS 14, when we are receiving some JavaScript calls from WKWebView, we can also provide a response easily with a reply handler. Thanks for the help.

Thank you for your prompt reply. Okay, I see, but I can't use insecure WebSocket if I am in the WKWebView with HTTPS because of mixed-content, correct ? By does the work, you mean using WKScriptMessage to communicate with the javascript from the web page in the web view and communicate with my WebSocket server underneath or completely get rid of the WebSocket server ? Thanks. Christophe

Hi, Thank you very much for your answer, it's clear. Okay, thanks, it would be great to be able to specify only certain cipher suites. Christophe B.

Hi,Thanks for the reply, I understand.I have seen the tls_ciphersuite_t enum but it does not help with knowing what cipher suites are supported by default when I call NWProtocolTLS.Options initializer.So, when using NWProtocolTLS.Options initializer, I have no way to retrieve the list of cipher suites that are enabled by default in the current environment, correct ? Therefore, I cannot restrict to some specific cipher suites if I wanted to ? I can only append ones from tls_ciphersuite_t enum ? Thanks, Christophe B.