StreamName. Nor can you configure watermarking, transcoding, recording, screenshot, or porn detection tasks for the playback domain.
Origin Server Information
Origin Server Type
Supports two types: Live Streaming Origin Server and StreamPackage.
Supports RTMP, HTTP-FLV, and HLS protocols.
If the FLV or HLS protocol is used, you can enable HTTPS.
If you enable HTTPS, port 443 will be used. Post-redirection HTTPS is also supported. There are no port restrictions.
Primary origin server
The address of the primary origin server, which can be an IP address or domain. You can also configure a backup origin server. The addresses will be polled.
Backup origin Server
The address of the backup origin server (optional).
Origin server host header
By default, the origin server address is used as the Host header if it is not configured.
http://xx001.elementtest.org/index.m3u8, because the resource is not yet cached in Tencent Cloud, CSS will resolve the domain
test001.comto get the server address of the origin server. Suppose it is
22.214.171.124. CSS will access the
126.96.36.199server, find the
index.m3u8file in the web server
test002.com, and then return the resource to the user.
If you enable this, Tencent Cloud will not cache the 301 or 302 status code. When 301 or 302 is returned by the origin server, Tencent Cloud will automatically redirect until it obtains the requested resource (max 10 redirects) and return the resource to the user. No redirects are needed on the user end.
If you disable redirection, Tencent Cloud will return the 301 or 302 status code to the user end, which will redirect to get the resource.
Pass-through of origin server URL parameters
By default, URL parameters are not passed through. If you enable this, parameters may be added to the URL without performing URL encoding or decoding.
HTTP request header pass-through
By default, HTTP request headers are not passed through. You can enable this to pass through the headers. Duplicate headers (case-insensitive) are not supported currently.
HTTP response header pass-through
By default, HTTP response headers are not passed through. You can enable this to pass through the headers. Duplicate headers (case-sensitive) are supported currently.
By default, GET request is supported, and Option request is supported after enabling it.
Index file cache time
The time to cache the index file when the origin server returns the 200 status code. The default cache time is 1,000 ms. The maximum time that can be set is 60,000 ms.
Segment cache time
The time to cache the TS/M4S/MP4 segments when the origin server returns the 200 status code. The default cache time is 1,000 ms. The maximum time that can be set is 60,000 ms.
Cache time by status code
When the origin server returns a non-200 status code, if it is unable to handle it immediately, and you don’t want to pass through all subsequent requests to the origin server, you can cache the status code and return it directly to the user. This can reduce the load on the origin server.
Currently, the following status codes can be cached, regardless of the file type:
4XX: 400, 403, 404, 405
5XX: 500, 503, 504
/test01, the rewriting rule will be applied to all requests under
/test01. Regular expressions are not supported currently.
/test01/test02, all requests under
/testwill be rewritten to
/test01/test02. Regular expressions are not supported currently.
The timeout period for establishing a TCP connection. The default time is 10,000 ms, and the value range is 2000-60000 (ms).
Please set the timeout period according to your origin server conditions and network conditions. If the timeout period is too short, when a pull request fails due to network issues, CSS may switch origin servers too frequently. If the timeout period is too long, CSS may wait a long time before it tries a different origin server, causing playback failure at the client end.
The maximum number of retry attempts. If multiple origin server addresses have been configured, when a request fails, CSS will try a different address.
Value range: 1-10.