Example; Parent.config - HP P4535A - Web Cache Server Appliance Administrator's Manual

Appendix D
Tag
interface

Example

The following example configures Traffic Server to block all requests from
:
rec.soccer
.block rec.*,!rec.soccer,
The following examples define pull and pullover groups.
comp.qqqq.com:9999 comp.* feed 10.3.3.2
news.qqqq.com * 2
NOTE

parent.config

The
parent.config
allows you to:
Set up parent cache hierarchies, with multiple parents and parent failover
Configure selected URL requests to bypass parent proxies
Description
pullover
The Traffic Server actively pulls the overview database for the news groups, but
retrieves news articles on demand.
NOTE: A "pullover" line in
"cache on demand" line. The Traffic Server needs to be aware of the news server
and its groups before it can pull overviews from a specific group. See the examples
following this table.
dynamic
The Traffic Server automatically decides, based on usage patterns, whether a group
should be "pull", "pullover", or demand retrieval-based.
Enter a positive integer
The Traffic Server retrieves articles on demand from the specified server according
to the assigned priority. The default priority is 0. Multiple servers assigned the
same priority are accessed in a round-robin fashion.
post
Articles to be posted to the specified news groups are sent to the specified server.
Enter the network interface the Traffic Server uses to contact the parent NNTP
server.
Every line designating a pull or pullover group must be preceded by a cache on demand
line as follows:
comp.webhost.com alt.*
comp.webhost.com alt.bicycles pull
news.hp.com ink.*
news.hp.com ink.* pullover
file identifies the HTTP parent proxies used in an HTTP cache hierarchy. This file
must be preceded by a
nntp_servers.config
rec.*
Configuration Files
groups, except for
179