(Namespace) Delivery Protocol {Http | Rtsp} Origin-Fetch - Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual

Administrator’s guide and cli command reference
Table of Contents

Advertisement

Media Flow Controller Administrator's Guide
status
make large changes, like the match value.
inactive by default; you must explicitly activate it.
virtual-player <name>
way, that namespace uses the specified virtual-player settings rather than the default
Media Flow Controller settings configured with the
no virtual-player to remove. See
show namespace {list | <namespace_name>}
List the list of namespaces in the system, or details of a given namespace. When used with
<namespace_name>, the output relevant to the namespace, such as the Active status,
Precedence, URI Prefix, Delivery Protocol, Domain, Origin Server and options, Virtual Player
(if any), Origin Fetch configuration, and Pre-stage FTP configuration, is given.
Note!
Configuration changes, including a namespace deletion, may not be updated for up to
30 seconds. This is due to a deferred update scheme that requires an HTTP request. An
internal probe ensures that such a request occurs at least every 30 seconds.

(namespace) delivery protocol {http | rtsp} origin-fetch

namespace <name> delivery protocol {http | rtsp} origin-fetch
byte-range
cache-age
cache-age-default <seconds>]
cache-directive no-cache {follow | override}
cache-fill {aggressive | client-driven}
content-store media [cache-age-threshold <seconds>] [object-size <bytes>]
date-header modify {deny | permit}
eod-on-close {disable | enable}
(Optional) Specify a list of policies for data fetched from origin (delivery protocol http or
rtsp); enters you to namespace <name> delivery protocol {http | rtsp} origin-fetch prefix
mode; use exit to leave. Use no namespace <name> delivery protocol {http | rtsp} origin-
fetch to re-set configured values to defaults.
Notes:
byte-range
ignore
preserve
request to be modified for optimization. Use no-align to disallow modification.
cache-age content-type <string><seconds>
cache aging by content-type <string> or the keyword content-type-any, and set a time
value in seconds. Re-enter the command as needed. Example cache-age content-type
entries: application/flv 28800, application/mov 2880, application/3gp 288,
application/f4v 28. If the cache-age content-type-any argument is unspecified, the
cache-age-default value is used. See
origin-fetch cache-age" on page 85
cache-age-default
fetched from the origin server. May be specified in addition to four content-type
—Make active or inactive the namespace; you must deactivate the namespace to
—Associate a defined virtual player with a namespace; in this
{preserve {align | no-align} | ignore}
{content-type <string> <seconds> | content-type-any <seconds>}
—(delivery protocol http only) Set request byte-range handling options.
—The received byte-range request is ignored and the entire file is fetched.
—The byte-range request is preserved; use align (default) to allow the
—Specify a cache age value in case it is not specified in the data
Media Flow Controller CLI Commands
Important!
A newly-created namespace is in
network
virtual-player
for CLI details.
—(delivery protocol http only) Set
"Using namespace delivery protocol <protocol>
for implementation details.
(namespace) delivery protocol {http | rtsp} origin-fetch
connection commands. Use
339

Advertisement

Table of Contents
loading

This manual is also suitable for:

Media flow controller 2.0.4

Table of Contents