Media Flow Controller Configuration Tasks (Web Interface)
Figure 53
Service Config > Namespace Configure Page Detail (Origin Server Configuration)
Configuring Namespace HTTP Match Details (Web Interface)
Refine the path of incoming requests (enclose all regex entries in single quotes). All match
options may utilize the optional precedence argument to break ties when namespaces are
defined with the same match criteria. Click Apply when done. See
To configure namespace HTTP Match Details:
1. Select the radio button as described and enter this information to the text boxes:
Precedence—Map incoming requests to a namespace, the lower the the precedence
number, the higher the preference for that namespace; 0 (zero) is default and highest; see
"Using namespace match <criteria> precedence" on page
•
Uri—Specify a uri-prefix match criteria for this namespace. See
page 34
•
•
•
Header—A header name and value; can also be a regex. Optionally, set a
precedence (defined above).
•
•
•
Query-string—A header name and value; can also be a regex. Optionally, set a
precedence (defined above).
•
•
182
Configuring NameSpaces (Web Interface)
for usage details.
uri-name—Enter a uri-prefix, use / (slash) for "any." See
page 30
for definition and example of uri-prefix.
uri-regex—Enter a regex to indicate the uri-prefix.
header-name and header-value
header-regex
query-name and query-value
query-regex
Media Flow Controller Administrator's Guide
Figure 54
84, for details.
"uri-prefix" on
"Terminology" on
Copyright © 2010, Juniper Networks, Inc.
Need help?
Do you have a question about the MEDIA FLOW CONTROLLER 2.0.4 - ADMINISTRATOR S GUIDE AND CLI and is the answer not in the manual?