Media Flow Controller Web-Based Interface : Service Config Tab : Service Config > NameSpace

Service Config > NameSpace
Create a namespace and set namespace options; these are set in the CLI with namespace.
Add Namespace
Enter a name for the new namespace and click Add Namespace. See Figure 78.
Figure 78 Service Config > Namespace Page Detail (Add Namespace)
Configuration List
Select a namespace and click Configure to open a new window and make configurations; click Show to see current settings; click Activate / Deactivate to take those actions. See Figure 79.
Figure 79 Service Config > Namespace Page Detail (Configuration List)
Namespace Configuration
Use this window to configure a new namespace or make changes to an existing one. After each configuration area, click Apply. When done click the close window icon.
Origin Server Configuration
Configure fetching content upon a cache-miss. In Release 2.0.2 only one (1) origin server is supported (either HTTP or NFS); multiple origin servers can be configured using a server-map; see namespace for CLI details. Click Apply when done. See Figure 80.
HTTP Origin—Use HTTP for origin-server delivery.
Hostname and Port—Use HTTP for origin-server delivery; multiple origin servers (up to 4) can be specified. Specify either a hostname as an FQDN (Fully Qualified Domain Name) or IP address. Specify a port number (default is 80).
Server-map—Enter the name of a server-map defined on the system. See server-map for CLI details; “Using namespace origin-server <protocol> server-map” on page 83 for task details.
Absolute-URL—Select to derive the origin server from the absolute URL set against the HTTP access method (GET, HEAD, etc.). Use absolute-url to configure Media Flow Controller as a mid-tier, proxy (if set, show namespace output has Proxy Mode: forward). Media Flow Controller uses the absolute URL to contact the origin-server. If absolute-url is configured and the incoming request (REQ header) does not have the absolute URL, then the request is rejected with the appropriate error code.
Follow-Header—Enter a header name, used in the incoming request, to be the origin server. For example, you could configure follow header HOST, and the value of the HOST header in the incoming request is used as the origin server. If the configured header does not exist, then the request is rejected. The <header name> can be any of the well-defined headers OR a custom header. If set, show namespace output has Proxy Mode: virtual. Note! In Release 2.0.2, only host is allowed.
NFS Origin—Use NFS for origin-server delivery.
Hostname and Port—Specify a port number (default is 2049) for that origin server.
Server-map—Enter the name of a server-map defined on the system. See server-map for CLI details; “Using namespace origin-server <protocol> server-map” on page 83 for task details.
Domain—Enter a FQDN (fully qualified domain name) or REGEX (regular expression) that is matched with the incoming HOST header. If there is a match, the request is refined with match value (next option). See “Using namespace domain <FQDN:Port>” on page 80 for implementation details.
Host—Domain name.
Regex—A regex to indicate the domain name.
Figure 80 Service Config > Namespace Configure Page Detail (Origin Server Configuration)
HTTP Match Details
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 Figure 81
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 81, for details.
Uri—Specify a uri-prefix match criteria for this namespace. See “uri-prefix” on page 31 for usage details.
uri-name—Enter a uri-prefix, use / (slash) for “any.” See “Terminology” on page 28 for definition and example of uri-prefix.
uri-regex—Enter a regex to indicate the uri-prefix.
Header—A header name and value; can also be a regex. Optionally, set a precedence (defined above).
header-name and header-value
Query-string—A header name and value; can also be a regex. Optionally, set a precedence (defined above).
query-name and query-value
Virtual-host—Enter the address and port (optional) of a virtual host.
virtual-IP and virtual-port—The IP address must be a /32 address; it can be 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 (defined above).
Figure 81 Service Config > Namespace Configure Page Detail (Match Details)
Parameters
Set cache inherit, status, virtual player, and delivery protocol options. See Figure 82.
Cache Inherit—Add the specified namespace’s cache to this one; see “Using namespace cache-inherit” on page 79, for details.
Status Active—Activate the namespace; de-select to de-activate but not delete.
Virtual Player—Assign an existing virtual player to this namespace; the virtual player settings override the global network connection settings (for this namespace).
Delivery Protocol—Set a protocol for responses from this namespace.
Figure 82 Service Config > Namespace Configure Page Detail (Parameters)
Pre-Stage User Configuration
Set a password for the auto-created FTP user for this namespace. See Figure 83.
New Password and Confirm Password—For each configured namespace FTP user (created automatically), set or reset a password.
Figure 83 Service Config > Namespace Configure Page (Pre-Stage User Configuration)
HTTP Origin Fetch
Configure options for HTTP fetching content from origin upon a cache miss. See Figure 84.
Cache Age Default—Specify a cache age value in case it is not specified in the data fetched from the origin server. Default is 28800 seconds (8 hours).
Date Header Modify Enable—Select to enable Media Flow Controller to set the Date header to the current time when the content is served to the client (no adjustments are made to the Cache-Control: max-age = <seconds> header, and the Age header sent from origin is maintained). De-select to disable (default); Media Flow Controller does not reset the Date header.
Cache Directive—Choose follow (default) to tell Media Flow Controller to obey the cache-directive (Cache-control : no-cache or Pragma: no-cache) in the HTTP header when data is fetched from the origin. Choose override to tell Media Flow Controller to always cache.
Content Store Media Cache Age Threshold—Set a time threshold for newly-fetched content stored in media cache (non-volatile) instead of RAM. By default, new content with a cache age under 60 seconds is stored only in RAM (the expectation is short cache-age implies that the content won’t be served for too long and is not worth storing in media cache). To have new content always stored in media cache, set this value to 0 (zero).
Figure 84 Service Config > Namespace Configure Page (HTTP Origin Fetch Configuration)
RTSP Origin Fetch
Configure options for RTSP fetching content from origin upon a cache miss. See Figure 85.
Cache Age Default—Specify a cache age value in case it is not specified in the data fetched from the origin server. Default is 28800 seconds (8 hours).
Cache Directive—Choose follow (default) to tell Media Flow Controller to obey the cache-directive (Cache-control : no-cache or Pragma: no-cache) in the HTTP header when data is fetched from the origin. Choose override to tell Media Flow Controller to always cache.
Content Store Media Cache Age Threshold—Set a time threshold for newly-fetched content stored in media cache (non-volatile) instead of RAM. By default, new content with a cache age under 60 seconds is stored only in RAM (the expectation is short cache-age implies that the content won’t be served for too long and is not worth storing in media cache). To have new content always stored in media cache, set this value to 0 (zero).
Figure 85 Service Config > Namespace Configure Page (RTSP Origin Fetch Configuration)

Report an Error
Media Flow Controller Administrator's Guide and CLI Command Reference
Copyright © 2010 Juniper Networks, Inc.