Configuring NameSpaces (Web Interface)
181
Media Flow Controller Administrator’s Guide
Media Flow Controller Configuration Tasks (Web Interface)
Configuring Namespace Origin Server (Web Interface)
Configure fetching content upon a cache-miss. In Release 2.0.4 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 53
.
To configure a namespace origin server:
1.
Enter this information to the text boxes or select the radio button as described:
•
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
“Creating
and Configuring Server-Maps (CLI)” on page 79
for task details.
•
Absolute-URL—Select to derive the origin server from the absolute URL set against
the HTTP access method (GET, HEAD, and so forth.). 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.4, 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;
“Creating and Configuring Server-Maps (CLI)” on page 79
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 the match value. See
“Using namespace domain <FQDN:Port>” on page 83
for
implementation details.
•
Host—Domain name.
•
Regex—A regex to indicate the domain name.
2.
Click Apply.
3.
Click Done at the bottom of the page if you are finished.
Содержание MEDIA FLOW CONTROLLER 2.0.4 -
Страница 6: ...Media Flow Controller Administrator s Guide VI Copyright 2010 Juniper Networks Inc...
Страница 24: ...LIST OF FIGURES XXIV Copyright 2010 Juniper Networks Inc...
Страница 37: ...Copyright 2010 Juniper Networks Inc 37 PART 1 Media Flow Controller Administration...
Страница 38: ...Media Flow Controller Administrator s Guide 38 Copyright 2010 Juniper Networks Inc...
Страница 285: ...Copyright 2010 Juniper Networks Inc 285 PART 2 Media Flow Controller Command and MIB Reference...
Страница 286: ...Media Flow Controller Administrator s Guide 286 Copyright 2010 Juniper Networks Inc...