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

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

Media Flow Controller Common Configuration Tasks (CLI) Media Flow Controller Administrator’s Guide
198 Configuring Caching All Contents for a Website (CLI) Copyright © 2010, Juniper Networks, Inc.
3. Set up DNS records so that incoming requests are routed to Media Flow Controller. Be
sure to set the Media Flow Controller DNS server so it is not the same as your Web
server’s DNS server (to prevent looping).
4. Configure a namespace with domain www.example.com and match uri-prefix / (slash):
test-vos (config) # namespace example
test-vos (config namespace example) # domain www.example.com
test-vos (config namespace example) # match uri /
test-vos (config namespace example) # origin-server http www.exampleOS.com
test-vos (config namespace example) # status active
test-vos (config namespace example) # exit
The match uri-prefix of just a / (slash) tells Media Flow Controller to use these
namespace rules for all incoming requests to domain www.example.com, since all
incoming requests have a / (slash) in them. To limit the application of these namespace
rules, you would change the match uri-prefix to narrow down which requests to that
domain trigger this namespace and set a precedence following the match criteria (the
lower the number, the higher the precedence) for resolving conflicts; a uri-prefix of just a /
(slash) would typically have a low precedence value configured so other namespaces
(which will all include a /) can be used.
Tip! If unsure what port you are using for origin-server, use standard Linux shell
commands to figure out the port, and then configure it along with the origin-server, if not
the default. If you need to change the origin-server, or any namespace setting, simply
enter the new setting.
Note! There are many namespace options, including cache-inherit, delivery protocol,
origin-fetch, and so forth. See “Creating a Namespace and Setting Namespace Options
(CLI)” on page 81 for more information and namespace for CLI details.
5. Repeat the configuration twice, if needed, to cover requests coming in to “example.com”
(without the “www” prefix) and the IP address for example.com (if requests may come in
that way).
6. Verify the configuration.
show namespace example
Namespace: example
Active: yes
Precedence: 0
Domain Name: www.example.com
Proxy Mode: reverse
Match Type:
URI-Prefix - /
Origin-Server: http://www.exampleOS.com:80
Delivery Protocol: HTTP Status Enabled: yes
Origin Fetch Configuration:
Cache-Age (Default): 28800 (seconds)
Cache Age Threshold: 60 (seconds)
Cache-Directive: follow
Object Size Threshold: NONE (Always Cached)
Modify Date Header: deny
Origin Request Configuration:
Cache-Revalidate: permit
Use 'Date' Header when Last-Modified is not present: no