Container.xml

Each container directory must have a container.xml file in order for it to be recognized as a stream container.

You can specify the security token and TTL settings in the container.xml file. These settings apply to set level manifests published to container. You can specify separate security tokens for PUT/POST and DELETE requests. You can also enable security token for PUT/POST and DELETE requests independent of each other. For example, you can enable a security token only for DELETE requests and disable it for PUT/POST requests or vice versa.

The following are sample contents of a container.xml file:

<Config>

<!-- Note that all the config specified here is applicable only on the container path and these 
settings are NOT inherited by the stream/vod modules under this container. To apply security or 
TTL settings on a stream/vod module, corresponding config must be applied in stream.xml/vod.xml
--> 

<!-- (Optional) Auth security applied to processing inbound PUT/DELETE requests on this container.    
<Auth> 
-->        

<!-- If the 'SecurityToken' element is present, then an auth test is applied to all inbound POST 
requests that will check for a valid X-Adobe-HDS-Token or X-Adobe-HTTP-Token request header with 
a valid token value. Requests not containing this header or passing an invalid or timed-out token 
value receive an error response of 401 Not Authorized. If the <SecurityToken> element is not present, 
this check is not performed.        
<SecurityToken> 
-->             

<!-- If <SecurityToken> element is enabled, it requires a valid AES-128 key to use for Token value 
encryption/decryption, and only Packager(s) configures with matching key can write to this Origin.  
-->            

<!-- <Key>4ff4756ed68239d34d482dbc88819abc</Key> -->             
<!-- Optional 'Timeout' for Token values in seconds. Default value is 600 seconds (10 minutes). 
If enabled, this value needs to be applied consistently here as well as at the Packager. -->            
<!-- <Timeout>600</Timeout> </SecurityToken>-->         

<!-- 
If the 'DeleteSecurityToken' element is present, then an auth test is applied to all inbound 
DELETE requests that will check for a valid X-Adobe-HDS-Token or X-Adobe-HTTP-Token request header 
with a valid token value.            

Requests not containing this header or passing an invalid or timed-out token value receive an error 
response of 401 Not Authorized. If the <DeleteSecurityToken> element is not present, this check is not 
performed. 
-->            

<!--
<DeleteSecurityToken>
              
If <DeleteSecurityToken> element is enabled, it requires a valid AES-128 key to use for Token value 
encryption/decryption, and only clients configured with matching key can delete from this Origin.             

<Key>4ff4756ed68239d34d482dbc88819abc</Key> 
-->             

<!-- Optional 'Timeout' for Token values in seconds. Default value is 600 seconds (10 minutes). If enabled, 
this value needs to be applied consistently here as well as at the Packager. -->            

<!-- <Timeout>600</Timeout> -->         
<!-- </DeleteSecurityToken> -->    
<!--</Auth> -->   
  
<HttpConfig>       

<!-- Uncomment following to override Server TTL settings for the GET requests made on this container path. 
<Headers>                
	<TTL>                   
	 <F4M>0</F4M>
	 <Bootstrap>0</Bootstrap>
	 <M3U8>0</M3U8>   
	 <Timeline>0</Timeline>
	 <DashManifest>0</DashManifest>
	 <DashManifestPart>0</DashManifestPart>
	</TTL>
</Headers> 
-->    

</HttpConfig>
</Config>