Using Namespace Delivery Protocol <Protocol> Origin-Fetch Cache-Age - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Media Flow Controller Administrator's Guide
Same as the case with match uri #2 (/abc), to map to ns2. Only match uri 3 ( / )should be
mapped to ns3 with the precedence value configured as shown.
Note! Excessive use of precedence has performance impact as precedence allows for
longest prefix matching. If possible, namespaces should be configured in such a way that they
have no overlaps in the domain and match <criteria> combination, which are used for
mapping the incoming HTTP GET to a namespace.
Using namespace delivery protocol <protocol> origin-fetch cache-age
The namespace <name> delivery protocol <protocol> origin-fetch cache-age argument
allows you to set granular cache aging policies based on content type, as well as a default
cache age. The cache-age for each content-type must be specified separately with positive
integers. Examples:
•
cache-age content-type-any 28800
Irrespective of content-type, override your configured cache-age-default or, if cache-age-
default is unconfigured, set the max-age for any content-type to 28800 seconds. If the
content request does not specify a max-age, set it to max-age 28800.
•
cache-age content-type application/flv 2880
cache-age-default 57900
When content-type is application/flv, set max-age to 2880 seconds. For all other content-
types use default configuration (57900 seconds in the example). If the received max-age
is set, use that value.
•
cache-age content-type application/flv 28800
cache-age content-type application/mov 2880
cache-age content-type application/3gp 288
cache-age content-type application/f4v 28
cache-age-default 57900
When content-type is application/flv, set max-age to 28800 seconds; for application/
mov, set max-age to 2880 seconds; for application/3gp, set max-age to 288; and for
application/f4v, set max-age to 28. For all other content-types use default configuration
(57900 seconds in the example). If the received max-age is set, use that value.
•
cache-age content-type application/qmx 60
cache-age content-type application/qss 288000
When content-type is application/qmx, set cache-age to 60 seconds, for application/
qss, set cache-age to 288000 seconds. For all other content-types use default
configuration: if max-age is not set in the data coming from origin, set it to the configured
default value (28800 if unspecified). If the received max-age is set, use that value.
Media Flow Controller Configuration Tasks (CLI)
Creating a Namespace and Setting Namespace Options (CLI) 85