Media Flow Controller Configuration Tasks (CLI)
Media Flow Controller Administrator’s Guide
90
Creating a Namespace and Setting Namespace Options (CLI)
Copyright © 2010, Juniper Networks, Inc.
nfs {<FQDN:export_path> [<port>] | server-map <name>}
rtsp {<FQDN> [<port#>]} [alternate <string> [<port#>]]
4.
Configure match criteria options (determines the URI to cache). All match options may
utilize the precedence argument to break ties when namespaces are defined with the
same match criteria. See
“Using namespace match <criteria> precedence” on page 84
,
for details.
match
header {<header> | regex <regex>} [precedence <number>]
query-string {<name> | regex <regex>} [precedence <number>]
uri <uri-prefix> | regex <regex>} [precedence <number>]
virtual-host <IP_address> [<port>] [precedence <number>]
•
header— (http only) A header name and value; can also be a regex. Optionally, set a
precedence.
•
query-string—(http only) A defined query param; can also be a regex. Optionally,
set a precedence.
•
uri—A <uri-prefix>; can also be a regex. See
“uri-prefix” on page 34
for uri-prefix
definition and usage details. Optionally, set a precedence.
•
virtual-host—The IP address must be a /32 address; it can take a special value of
0.0.0.0, which means any IP address. Port number specification is optional. To map
requests by TCP port number only, set the IP address to 0.0.0.0 and configure the port
number. If you set the domain to any, configure virtual-host IP to 0.0.0.0, then
requests can be assigned to a namespace based solely on the port number on which
the request comes in to Media Flow Controller. Optionally, set a precedence.
Note!
All regex values should be enclosed in single quotes; for example, a regex for
www.example.com plus example.com could be this: ‘^.*\example\.com’.
5.
Configure delivery protocol options; only origin-fetch options are available for rtsp.
Note!
To enable delivery protocol rtsp, press enter after rtsp; then set RTSP options.
•
client-request [cookie | query-string]—(http only) Optionally, set an action,
whether or not to cache (default), for cookies or objects with a query-string (such
objects are typically dynamic and often not appropriate for caching). For query-string
you can also opt to not cache the query-string itself.
client-request [cookie | query-string] action {cache [exclude-query-
string] | no-cache}
•
client-response—(http only) Optionally, configure client-response header actions.
Up to sixteen client-response headers and actions may be specified.
client-response header <name> [<value>] action {add | delete}
•
origin-fetch—Optionally, configure origin-fetch parameters for data fetched from
origin, including managing the cache, and modifying the Date header. See
(namespace) delivery protocol {http | rtsp} origin-fetch
for CLI details.
origin-fetch
cache-age {content-type<string> <seconds> | content-type-
any<seconds>}
cache-age-default <seconds>
cache-directive no-cache {follow | override}
content-store media [cache-age-threshold<seconds>] [object-
size<bytes>]
date-header modify {deny | permit}
•
origin-request—(http only) Optionally, configure parameters for data requested from
origin. See
(namespace) delivery protocol http origin-request
for CLI details.
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...
