Media Flow Controller CLI Commands : namespace : (namespace) delivery protocol {http | rtsp} origin-fetch

(namespace) delivery protocol {http | rtsp} origin-fetch
namespace <name> delivery protocol {http | rtsp} origin-fetch
byte-range {preserve {align | no-align} | ignore}
cache-age {content-type <string> <seconds> | content-type-any <seconds>}
cache-age-default <seconds>]
cache-directive no-cache {follow | override}
cache-fill {aggressive | client-driven}
content-store media [cache-age-threshold <seconds>] [object-size <bytes>]
date-header modify {deny | permit}
(Optional) Specify a list of policies for data fetched from origin (delivery protocol http or rtsp); enters you to namespace <name> delivery protocol {http | rtsp} origin-fetch mode, use exit to leave, use no namespace <name> delivery protocol {http | rtsp} origin-fetch to re-set configured values to defaults. Notes:
byte-range—(delivery protocol http only) Set request byte-range handling options.
ignore—The received byte-range request is ignored and the entire file is fetched.
preserve—The byte-range request is preserved; use align (default) to allow the request to be modified for optimization. Use no-align to disallow modification.
cache-age content-type <string><seconds>—(delivery protocol http only) Set cache aging by content-type <string> or the keyword content-type-any, and set a time value in seconds. Re-enter the command as needed. Example cache-age content-type entries: application/flv 28800, application/mov 2880, application/3gp 288, application/f4v 28. If the cache-age content-type-any argument is unspecified, the cache-age-default value is used. See “Using namespace delivery protocol <protocol> origin-fetch cache-age” on page 82 for implementation details.
cache-age-default—Specify a cache age value in case it is not specified in the data fetched from the origin server. May be specified in addition to four content-type specifications. Default value is 28800 seconds (8 hours). See “Using namespace delivery protocol <protocol> origin-fetch cache-age” on page 82 for implementation details.
cache-directive—Specify what to do with the cache-directive header (Cache-Control : no-cache or Pragma: no-cache) in the HTTP header when data is fetched from the origin. Default is follow; use override to cache despite a no-cache header.
cache-fill—(delivery protocol http only) Specify how data is fetched.
aggressive—(default) Get all the data irrespective of how much the client requested; useful for reverse proxy namespace.
client-driven—Fetch only as much data as the client requested; useful for transparent proxy namespace.
content-store media—Set caching options.
cache-age-threshold—Set a time threshold for newly-fetched content stored in media cache (non-volatile) instead of RAM cache. By default, new content with a cache age under 60 seconds is stored only in RAM cache (the expectation being 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).
object-size—Set a size limit, in kilobytes, for storing objects in disk cache. For example, a value of 4 means store in disk cache all fetched objects larger than 4 bytes; a value of 0 (zero) (default) means every object irrespective of size is cached in disk (if not marked non-cacheable in the Cache-Control header). If the object size is less than this threshold, it is served from Media Flow Controller’s RAM cache. Setting object-size can improve disk-cache performance since small objects need not be written into disk and can be served directly from the RAM cache.
date-header modify—(delivery protocol http only) Allow (with permit) or disallow (with deny, the default) Media Flow Controller to modify the Date Header for content fetched from origin. If set to permit, Media Flow Controller resets the Date header when the content is received; however, no adjustments are made to the Cache-Control: max-age = <seconds> header, and the Age header and Via header sent from origin are maintained as-is. May be useful if Media Flow Controller is deployed as a server.

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