Configure Your Origin With Nimble Streamer
The Flink OTT Client SDK will slightly alter the way how client devices request data from your CDN. Instead of typical HTTP GET calls, they will use HTTP Range Requests 🔗.
Please Note: The correct setup of your infrastructure may depend on both your streaming origin's configuration and/or your CDN's configuration. For example, some CDNs pass through all HTTP headers they receive from the origin while other CDNs add, remove or replace existing HTTP headers. To ensure the correct setup, please keep in mind that some CDN providers can override or alter your origin HTTP headers. This means, that in some cases, Step 1 and Step 2 of this guide can interfere with each other.
Modern web and streaming servers support range requests by default. However, you might want to ensure that your streaming origin / CDN meets the following requirements:
CORS OPTIONS Request Support
CORS Preflight requests (HTTP OPTIONS requests) must be supported. Verification:
curl -i -X OPTIONS <your manifest URL> must contain an
ALLOWED header in which
OPTIONS must be listed.
curl -X OPTIONS http://example.org -i HTTP/1.1 204 No Content Allow: OPTIONS, GET, HEAD, POST
HTTP Range Request Support
HTTP Range Requests 🔗 must be allowed. This means, when sending a CORS OPTIONS request, your server must respond with a
Access-Control-Allowed-Headers header in which
Range must be listed.
curl -X OPTIONS http://example.org -i HTTP/1.1 204 No Content Access-Control-Allowed-Headers: Range
Nimble Streamer Configuration
Step 1 - Update Configuration File
Add the following to your
# CORS settings for Strive integration access_control_allow_origin = * access_control_allow_credentials = true access_control_allow_headers = Range access_control_expose_headers = Content-Length
The next step is to configure your CDN 🔗.