Yes. When using the iostream/raw transport, there are no TLS features and OPENSSL is not required. When using the Asio transport TLS features are optional. You only need OpenSSL if you want to use TLS. You can only make or recieve encrypted connections (https/wss) if you have enabled TLS features.

Whether an Asio endpoint uses TLS or not is determined by its config TEMPLATE parameter. The default bundled websocketpp::config::asio and websocketpp::config::asio_client configs do not SUPPORT TLS, the websocketpp::config::asio_tls and websocketpp::config::asio_tls_client do.

The <websocketpp/config/asio.hpp&GT; and <websocketpp/config/asio_client.hpp> HEADERS will include both the TLS and non-TLS varients of their respective configs and require the presence of OpenSSL. The <websocketpp/config/asio_no_tls.hpp> and <websocketpp/config/asio_no_tls_client.hpp> headers will include only the non-TLS configs and do not require OpenSSL.

Yes. When using the iostream/raw transport, there are no TLS features and OpenSSL is not required. When using the Asio transport TLS features are optional. You only need OpenSSL if you want to use TLS. You can only make or recieve encrypted connections (https/wss) if you have enabled TLS features.

Whether an Asio endpoint uses TLS or not is determined by its config template parameter. The default bundled websocketpp::config::asio and websocketpp::config::asio_client configs do not support TLS, the websocketpp::config::asio_tls and websocketpp::config::asio_tls_client do.

The <websocketpp/config/asio.hpp> and <websocketpp/config/asio_client.hpp> headers will include both the TLS and non-TLS varients of their respective configs and require the presence of OpenSSL. The <websocketpp/config/asio_no_tls.hpp> and <websocketpp/config/asio_no_tls_client.hpp> headers will include only the non-TLS configs and do not require OpenSSL.