Streaming Media Supplement sa2150 and sa2250

99
Chapter 9 Configuring Media-IXT for QuickTime
For selective caching and filtering rules for QuickTime that use url_regex, include the port number. For
example, if you are filtering requests for a clip called clip.rm at bad.content.com, the correct rule to
use would be this:
url_regex=bad.content.com:554\/clip.rm action=deny
Secondary specifiers
Besides the single primary specifier, one or more secondary specifiers may also be added:
• port, meaning port on the origin server. Example:
port=8080
• scheme, meaning the protocol in use. Example:
scheme=rtsp
• prefix, meaning a prefix in the path part of a URL. Example:
prefix=/someclips
• method, meaning a URL request method. Possible values:
get, post, put, trace
• time, meaning a time range. Example:
08:00-14:00
The allow and deny actions
For filter.config, you must assign one of the two following actions:
action=allow
action=deny
(The other possible actions in filter.config have no effect on Media-IXT.)
The example filter.config rules below deny proxy access to all deniedtome.com sites except for
vetted.deniedtome.com:
dest_host=vetted.deniedtome.com action=allow
dest_domain=deniedtome.com action=deny
Modifying the cache.config file to determine cacheability
To limit streaming media caching to specific URLs, you must specify caching rules in the cache.config
file located in Traffic Server’s config directory.
For cache.config, you must assign one of the two following actions:
action=never-cache
action=standard-cache
(The other possible actions in cache.config have no effect on Media-IXT.)
Caching rules apply to HTTP, RTSP, and MMS URLs. You can use the suffix secondary specifier with the
values .rm, .sdp, .asf or other file extensions to limit a rule to those particular file formats. You can also
use the scheme secondary specifier, along with tags where needed, to limit a rule to a particular streaming
format.
See the description of url_regex in the section about filter.config above; use of url_regex with
cache.config works the same way.
In the example below, the first rule allows RealNetworks content from music.com to be cached and the
second rule prevents .rm files from all other sites from being cached.