# Query String Handling

## Default Query String Settings

You can control the fundamental operations of Low-Latency HLS (or Legacy HLS) via the `<DefaultQueryString>`.

Set in `<Publishers><LLHLS><DefaultQueryString>` (or `<Publishers><HLS><DefaultQueryString>`) in `Server.xml` as follows:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<Server version="8">
  ...
  <VirtualHosts>
    <VirtualHost>
      <Applications>
        <Application>
          <Publishers>
            ...
            <LLHLS>
              <DefaultQueryString>
		        <Query>
				  <Key>_HLS_legacy</Key>
				  <Value>NO</Value>
		        </Query>
		        <Query>
				  <Key>_HLS_rewind</Key>
				  <Value>YES</Value>
			    </Query>
			  </DefaultQueryString>
            </LLHLS>
          </Publishers>
        </Application>
      </Applications>
    </VirtualHost>
  </VirtualHosts>
</Server>
```

{% hint style="info" %}
This setting is ignored if the playback URL already has a query string appended to it.
{% endhint %}

<table><thead><tr><th width="151">Key</th><th width="138">Value</th><th>Description</th></tr></thead><tbody><tr><td>_HLS_legacy</td><td>YES | NO <br><mark style="color:yellow;">* Default: NO</mark></td><td>Sets the <code>_HLS_legacy</code> value to <code>YES</code> will remove partial segment information from LL-HLS playlists, making them work the same as legacy HLS like HLSv6.<br><mark style="color:orange;">* LL-HLS Only</mark></td></tr><tr><td>_HLS_rewind</td><td>YES | NO<br><mark style="color:yellow;">* Default: YES</mark></td><td>If the <code>_HLS_rewind</code> value is set to <code>YES</code> and the <a href="https://airensoft.gitbook.io/ovenmediaengine/streaming/low-latency-hls#live-rewind">Live Rewind</a> feature is enabled, old segment information will be included in the playlist.</td></tr></tbody></table>

## Using Propagate Query String

When you enable `<PropagateQueryString>`, the query string included in the initial Master Playlist request is automatically carried over to all sub-requests (Media Playlist, Segment, and Partial Segment). By including session keys, authentication tokens, etc., in the query string and utilizing this feature, content access control becomes easier as all requests can be verified at the CDN level.

Set the `<Publishers><LLHLS><PropagateQueryString>` (or `<Publishers><HLS><PropagateQueryString>`) in `Server.xml` like this:

```xml
<?xml version="1.0" encoding="UTF-8"?>
<Server version="8">
  ...
  <VirtualHosts>
    <VirtualHost>
      <Applications>
        <Application>
          <Publishers>
            ...
            <LLHLS>
              <OriginMode>true</OriginMode>
              <PropagateQueryString>true</PropagateQueryString>
            </LLHLS>
          </Publishers>
        </Application>
      </Applications>
    </VirtualHost>
  </VirtualHosts>
</Server>
```

{% hint style="danger" %}
You should take care not to include sensitive information in the Query String directly.
{% endhint %}


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://ovenmediaengine-enterprise.gitbook.io/guide/features/workflow-integration-and-external-system-connectivity/query-string-handling.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.