Juniper MEDIA FLOW CONTROLLER 2.0.4 -, Administrator'S Manual

Page: 340 / 400

Media Flow Controller CLI Commands Media Flow Controller Administrator’s Guide
340 (namespace) delivery protocol http origin-request Copyright © 2010, Juniper Networks, Inc.
specifications. Default value is 28800 seconds (8 hours). See “Using namespace delivery
protocol <protocol> origin-fetch cache-age” on page 85 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 will not 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 the Media Flow Controller 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.
•
eod-on-close
—(delivery protocol http only) Enable or disable the option to detect the
end of data in case the origin is a transcoder that provides an invalid content-length in the
beginning of the fetch. When enabled, this option uses the “connection close” from origin
as end of data and modifies the content length to the actual length received when caching
the object.
(namespace) delivery protocol http origin-request
namespace <name> delivery protocol http origin-request
cache-revalidation {deny | permit [use-date-header]}
connect timeout <seconds> retry-delay <seconds>
header <name> [<value>] action add ...
host-header inherit incoming-req {deny | permit}
read interval-timeout <seconds> retry-delay <seconds>
x-forwarded-for {disable | enable}