In the preceding process, HTTPDNS is used in the third step.
For the duration of the SSL session or TLS session, the server and the client can exchange messages that are encrypted by using the secret key. The SSL server or TLS server obtains the encrypted random byte string by using the private key.Ī session ticket that can be used as a secret key is generated based on the preceding process. The SSL client or TLS client verifies the public key certificate of the server, and sends the random byte string that is encrypted by using the public key of the server. The SSL server or TLS server receives the handshake request, selects an applicable algorithm, and then sends the public key certificate and random byte string. The SSL client or TLS client sends a handshake request that contains a random byte string and a list of supported algorithms. The following section describes the procedure for completing a handshake: To send an HTTPS request, your server must complete an SSL handshake or Transport Layer Security (TLS) handshake. We recommend that you access HTTPDNS by referring to Use HTTPDNS and OkHttp to connect an Android app to an IP address. This solution is simpler and more versatile than the general solution. If you use OkHttp as the network development framework, you can elegantly connect your Android app to an IP address by means of a DNS service customization API provided by OkHttp.
#Handshaker app for android how to
This topic describes how to connect an Android app to an IP address that is resolved from HTTPDNS in HTTPS scenarios, including scenarios in which SNI is required.
For more information about the resolution service provided by HTTPDNS, see the SDK for Android development manual. This topic describes how to connect an Android app to an IP address that is resolved from HTTPDNS in HTTPS scenarios, including scenarios in which Server Name Indication (SNI) is required.
0 kommentar(er)
