Using HTTP(s) over the SUPMessagingChannel

(Optional) Clients can securely communicate with the backend via the server through the HTTPS transport protocol. By using SSL over the SUPMessagingChannel, all messages are encrypted and authenticated to ensure secure communication.

• Enabling HTTP(S) as a Transport Protocol
  (Optional)You can set HTTP(S) as the transport protocol that the an OData client should use to communicate with a network edge (Example: Relay server).
• Enabling a Listener for HTTPS Support with Server Certificate Validation
  (Optional) For a HTTPS protocol, when a client attempts to setup a trusted connection with the host (like a relay server), the host responds with a certificate. To verify if the server certificate is trusted or not, the application registers a delegate with the OData SDK. If the server certificate is trusted, the connection is successful. If the server certificate is not trusted, the delegate determines if the certificate should be deemed trusted and proceed with the connection.If no delegate is set, all certificate chains that are not automatically trusted are rejected.
• Enabling a Listener for HTTP(S) Support with Basic Auth Challenge
  (Optional) For a HTTP(S) protocol, when a client attempts to setup a trusted connection with the host (like a relay server), the host responds with a certificate. To verify if the server certificate is trusted or not, the application registers a delegate with the OData SDK. If the server certificate is trusted, the connection is successful. If the server certificate is not trusted, the delegate determines if the certificate should be deemed trusted and proceed with the connection.If no delegate is set, all certificate chains that are not automatically trusted are rejected.
• Registering a Listener for HTTP Errors in iOS Applications
  To ensure that OData iOS clients are notified of HTTP errors while establishing a connection with the network edge, implement a listener.