(namespace) delivery protocol {http | rtsp} origin-fetch
339
Media Flow Controller Administrator’s Guide
Media Flow Controller CLI Commands
•
status
—Make active or inactive the namespace; you must deactivate the namespace to
make large changes, like the match value.
Important!
A newly-created namespace is in
inactive by default; you must explicitly activate it.
•
virtual-player <name>
—Associate a defined virtual player with a namespace; in this
way, that namespace uses the specified virtual-player settings rather than the default
Media Flow Controller settings configured with the
network
connection commands. Use
no virtual-player to remove. See
virtual-player
for CLI details.
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 {preserve {align | no-align} | ignore}
cache-age {content-type <string> <seconds> | content-type-any <seconds>}
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
—(delivery protocol http only) Set request byte-range handling options.
•
ignore
—The received byte-range request is ignored and the entire file is fetched.
•
preserve
—The byte-range request is preserved; use align (default) to allow the
request to be modified for optimization. Use no-align to disallow modification.
•
cache-age
content-type <string><seconds>
—(delivery protocol http only) Set
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
“Using namespace delivery protocol <protocol>
origin-fetch cache-age” on page 85
for implementation details.
•
cache-age-default
—Specify a cache age value in case it is not specified in the data
fetched from the origin server. May be specified in addition to four content-type
Summary of Contents for MEDIA FLOW CONTROLLER 2.0.4 -
Page 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Page 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Page 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Page 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Page 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Page 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...
