Media Flow Controller Configuration Tasks : How To : Configure HTTP Fetch for Videos

Configure HTTP Fetch for Videos
Configuring Media Flow Controller to fetch all video files, located in a particular directory on the origin server, via HTTP, requires another namespace configuration.
In this example, all requests for videos at www.example.com/videos/ that incur a cache miss (necessitating an origin fetch) are fetched from the specified origin using HTTP.
For our example company, www.example.com, the configuration could look like this:
test-vos (config) # namespace exampleVideos
test-vos (config namespace exampleVideos) # domain www.example.com
test-vos (config namespace exampleVideos) # match uri /videos/
test-vos (config namespace exampleVideos) # origin-server http www.exampleOS.com 80
test-vos (config namespace exampleVideos) # status active
test-vos (config namespace exampleVideos) # exit
test-vos (config) #
The match uri-prefix of /videos tells Media Flow Controller to use these namespace rules for incoming requests containing /videos in the URL: use HTTP to fetch the requested file from the specified origin-server on port 80 (HTTP default).
Just as with the initial namespace configuration, repeat the namespace configurations with the domain specified without the “www” prefix, and again specified with the IP address, if requests may come in those ways.
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.

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