Skip to main content

Query String Forwarding: forward parameters to sub-requests

What is Query String Forwarding?

Query String Forwarding copies selected query string parameters from a parent file request to nested file requests. It is mainly used for HLS and MPEG-DASH video, where a viewer requests a master manifest first, and that manifest references rendition manifests, media segments, subtitles, or other related files.

For example, a viewer can request a protected HLS master manifest with a secure token:

https://demo-files-protected.gvideo.io/coffee_run/master.m3u8?md5=n9cVLrZoiK0wj-CANW3fyw&expires=1777545540

With enabled Query String Forwarding the CDN automatically inserts the forwarded query string parameters into manifest bodies. For secure token parameters like md5 and expires are required.

Query string parameters are inserted into manifest body links automatically

As the result, the video player doesn't need to operate with tokens for each file, as it reads data from modified manifests instead.

Query string parameters are forwarded from the master manifest to nested manifests and segments

Configure in the Customer Portal

To configure Query String Forwarding in the CDB Technical Web Portal:

  1. Go to CDN and select the CDN resource you want to configure.
CDN resource list
  1. In the sidebar, under the Content section, click Query String Forwarding.
  2. Enable the option.
  3. In Forward from file types, add m3u8 and mpd.
  4. In Forward to file types, add ts, mp4, m3u8, m4s, and vtt.
  5. In Forward only keys, add md5 and expires.
  6. Save the CDN resource.

Configure by API

Use the same values when updating a CDN resource by API.

For video-specific setup, recommended file types, and Secure Token path rules, see Secure token for video.