Juniper MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI Administrator's Manual page 337

Media Flow Controller Administrator's Guide
•
delivery protocol
may be configured. Entering the delivery protocol puts you into namespace delivery
protocol configure mode; use exit when finished.
•
http
•
•
•
•
•
rtsp
•
•
domain
expression) is matched with the incoming HOST header. If there is a match, the request is
refined with match value. See
"Using namespace domain regex" on page 82
•
any
•
regex
all regex entries in single quotes; for example, a regex for www.example.com plus
example.com could be this: '^.*\example\.com'.
•
FQDN
enter should match whatever you have configured as HOST header; you may append
a port number as well, if needed (and used in HOST header).
—Set delivery protocol options; two delivery protocols and options
—Configure options for HTTP delivery:
—Manipulate incoming client requests:
client-request
−
cache-control max-age <number> action serve-from-origin
Max-Age value for the incoming request Cache-Control header. Default is 0
(zero) which invalidates the incoming Max-Age value causing a data fetch
from origin.
−
cache-hit action revalidate-always
only. Specify that requested objects in cache always trigger a time-stamp
revalidation. Default is disabled.
revalidate all command is not executable when revalidate-always is
configured as it is configurable only for T-proxy namespaces.
−
—Set an action for objects with a cookie (cookies are typically
cookie action
dynamic and often not appropriate for caching); either cache or no-cache
(default).
−
query-string action
objects are typically dynamic and often not appropriate for caching); either
cache (and, optionally, exclude-query-string itself from the cache) or no-
cache (default).
—Manipulate headers in incoming client responses. Up to
client-response
sixteen header actions can be set; either add or delete.
header <name>, the only action allowed is delete; if you enter a header <name>
and <value>, the only action allowed is add.
—Set policies for content fetched from origin; see
origin-fetch
delivery protocol {http | rtsp} origin-fetch,"
—Set policies for content requested from origin; see
origin-request
"(namespace) delivery protocol http origin-request,"
— Configure options for RTSP delivery:
—Set policies for content fetched from origin; see
origin-fetch
delivery protocol {http | rtsp} origin-fetch,"
—The defined FQDN (fully qualified domain name) or REGEX (regular
(default)—Allow all domains to use this namespace.
— Set the domain for this namespace with a regular expression.
—Enter a Fully Qualified Domain Name (FQDN).
Note! The namespace <name> object
—Set an action for objects with a query-string (such
for CLI details.
for CLI details.
"Using namespace domain <FQDN:Port>" on page 83
for task details.
Media Flow Controller CLI Commands
—Transparent proxy namespaces
Note! If you enter only a
"(namespace)
for CLI details.
"(namespace)
Note!
Important! The domain you
namespace
—Set a
and
Enclose
337