ApsaraVideo Live:HTTPS settings

Introduction

Hyper Text Transfer Protocol over Secure Socket Layer (HTTPS) is a secure HTTP channel that uses the SSL or TLS protocol for encapsulation. ApsaraVideo Live provides HTTPS to securely accelerate content delivery. You can view, disable, enable, and edit certificates. If a certificate is correctly configured and enabled for a domain, both HTTP and HTTPS requests are supported. If the certificate does not match the domain or is disabled, only HTTP requests are supported.

Benefits of HTTPS

• Encrypts sensitive information, such as session IDs and cookies, during transmission. This prevents security risks, such as information leakage, if the data is intercepted by attackers.

• HTTPS verifies data integrity during transmission to protect against man-in-the-middle (MITM) attacks, such as DNS and content hijacking or tampering.

Usage notes

Step 1: Purchase a certificate

To enable Enable HTTPS, you need a certificate that matches your streaming domain. If you do not have one, go to Certificate Management Service and click Buy Now. If you have a custom certificate, you can skip this step.

Step 2: Configure a streaming domain

1. Enable HTTPS.

   1. Log on to the ApsaraVideo Live console.

   2. In the left navigation pane, click Domain Names. The Domain Management page appears.

   3. Find the streaming domain for which you want to configure HTTPS and click Domain Settings in the Actions column.

   4. Click HTTPS Settings and turn on the HTTPS Certificate switch.

2. Select a certificate.

   • Certificate from Certificate Management Service: For Certificate Type, select Alibaba Cloud Security. Select the certificate that you purchased from Certificate Management Service. You can select it by name to match the streaming domain.

   • Custom certificate: For Certificate Type, select Others. Enter a certificate name, and then upload the certificate content and private key. The certificate is saved in the Certificate Management Service console and can be viewed in the My Certificates section.

     Note

     Only certificates in PEM format are supported.

Introduction

HTTP/2, also known as HTTP 2.0, introduces features such as multiplexing, header compression, request prioritization, and server push. It addresses the limitations of HTTP 1.1 to optimize request performance while remaining compatible with HTTP 1.1 semantics. Modern browsers such as Chrome, Edge, Safari, and Firefox support the HTTP/2 protocol.

Benefits of HTTP/2

• Binary protocol: Unlike the text-based parsing of HTTP 1.x, HTTP/2 splits all transmitted information into smaller messages and frames, and encodes them in a binary format. This binary foundation allows for greater protocol extensibility, such as introducing frames to transport data and commands.

• Multiplexing: In HTTP 1.x, performance optimizations often involve techniques like using image sprites and multiple domains because browsers limit the number of concurrent requests per domain. When a page needs to load many resources, head-of-line blocking can occur, which forces resources to wait for other requests to complete. In HTTP/2, the binary framing layer allows multiple requests and responses to be sent concurrently over a shared TCP connection. The recipient reassembles them by using stream identifiers and headers. This technique avoids the head-of-line blocking issue of older HTTP versions and greatly improves transmission performance.

• Header compression: HTTP request headers contain a large amount of repetitive information. HTTP/2 uses the HPACK format for compression. Both the client and server maintain an index table of header fields. Identical headers are transmitted by using only their index numbers, which improves efficiency and speed.

• Server push: A server can send multiple responses for a single client request. This allows the server to push resources to the client without the client explicitly requesting them.

Usage notes

Before you proceed, ensure that HTTPS is enabled.

Enable or disable HTTP/2

1. Log on to the ApsaraVideo Live console.

2. In the left navigation pane, click Domain Names. The Domain Management page appears.

3. Find the streaming domain that you want to configure and click Domain Settings in the Actions column.

4. In the left-side navigation pane for the domain, click HTTPS Settings.

5. In the HTTP/2 section, turn the HTTP/2 switch on or off.

Introduction

If you have enabled HTTPS for your streaming domain, you can configure a force redirect to automatically change the protocol of end-user requests.

For example, if you enable the HTTP > HTTPS redirect, when an end user makes an HTTP request, the server returns a 301 response that redirects the request to HTTPS. The following code provides an example.

$ curl http://xxx xxx xxx/' -i
HTTP/1.1 301 Moved Permanently
Server: Tengine
Date: Mon, 03 Jun 2019 13:26:01 GMT
Content-Type: text/html
Content-Length: 278
Connection: keep-alive
Location: https://xxx xxx xxx/
Via: cache2.cn201[,0]
Timing-Allow-Origin: *
EagleId: 2a786b0215595683612635433e
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<h1>301 Moved Permanently</h1>
<p>The requested resource has been assigned a new permanent URI.</p>
&lt;hr/&gt;Powered by Tengine</body>
</html>

Procedure

1. Log on to the ApsaraVideo Live console.

2. In the left navigation pane, click Domain Names. The Domain Management page appears.

3. Find the streaming domain that you want to configure and click Domain Settings in the Actions column.

4. In the left-side navigation pane for the domain, click Streaming Management > HTTPS Settings.

5. Click Change Settings.

   The Modify Configuration button is in the Force Redirect section.

6. Select a Redirect Type.

   After selecting a type, click OK.

   Redirect type	Description
   Default	Both HTTP and HTTPS requests are supported.
   HTTPS > HTTP	Requests from clients to points of presence (POPs) are redirected to HTTP.
   HTTP > HTTPS	Requests from clients to POPs are redirected to HTTPS to ensure secure access.

7. Click OK.

Certificate format conversion methods

HTTPS configuration only supports PEM-formatted certificates. Convert other formats to PEM using the OpenSSL tool. The following table shows common conversion methods.