Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Руководство администратора

Страница: 89 / 400

Creating a Namespace and Setting Namespace Options (CLI) 89
Media Flow Controller Administrator’s Guide Media Flow Controller Configuration Tasks (CLI)
proxy-mode transparent on-ip <IP_address_of_your_interface>
delivery protocol http
origin-request x-forwarded-for disable
origin-request host-header inherit incoming-req permit
origin-fetch content-store media object-size 32768
status active
exit
exit
Using namespace match virtual-host
You can specify a virtual host for the namespace match criteria; see Virtual Host for
definition. To do this, enter the IP address of the virtual host and, optionally, a port number;
you can also set a precedence, if needed. In this configuration, the incoming session's
destination IP is used to find the match to the namespace. In order for the match to be based
only on destination IP you should set domain to any. In that way, the incoming session's
destination IP and destination port (if given) are used to match to the namespace. Examples,
from namespace prefix mode:
• Match all sessions whose destination IP is 10.1.1.1 to the namespace:
match virtual-host 10.1.1.1
• Match all incoming HTTP REQ with destination IP 10.1.1.1 and port 8080 to this
namespace:
match virtual-host 10.1.1.1:8080
• Match all incoming REQ on destination port 8080 to this namespace:
match virtual-host 0.0.0.0:8080
Configuring Media Flow Controller Namespaces (CLI)
Configure namespaces to set fine-grained delivery policies; every Media Flow Controller
deployment must have at least one namespace, and usually several.
To configure a namespace:
1. Configure a namespace with a name (enters you to namespace configuration mode, use
exit when finished); optionally inherit another namespace’s cache or UUID. Use show
namespace list to find namespace UUIDs. See
namespace for CLI details.
namespace <name> [cache-inherit <namespace:UUID>]
2. Configure domain settings (default is any). Note! The domain you enter should match
whatever you have configured as HOST header, unless using regex; you may append a
port number as well if needed (and used in HOST header). See
“Using namespace
domain regex” on page 82 and “Using namespace domain <FQDN:Port>” on page 83 for
details.
domain {any | <FQDN> | regex <regex>}
3. Configure origin-server settings (example uses http); multiple origin servers can be
configured with the server-map option; port specification is optional. See
“Creating and
Configuring Server-Maps (CLI)” on page 79 , for more information. See (namespace)
origin-server for CLI details.
origin-server
http {absolute-url | follow {header <header> [use-client-ip] | dest-ip
[use-client-ip]} | server-map <map_name> | <FQDN/path> [<port>]}