proxy/config/prefetch.config.default

#prefetch.config
#example configuration file for prefetch.
#
# You need to have following line in records.config file to enable Prefetch
# feature
#	CONFIG proxy.config.prefetch.prefetch_enabled INT 1
#
#In this file we need to specify Traffic Server child node ip addresses.
#Prefetch will be applied to requests from those ip addresses:
#
# eg:
# prefetch_children 10.0.0.0 - 10.255.255.255, 216.1.2.3

#Providing separate set of html tags for parsing:
#
#There is already a default set of tags which is used by the Prefetch parser.
#If you don't provide any tags, these default tags will be used. If you provide
#even one html tag pair, only the html tag pairs provided here will be used. None
#of the tags in the default set is used:
# Format:
# each line should of the form:
#
# 	html_tag tag attr
#
#       or
#
#       html_tag tag attr filter_attr filter_value
#
# where 'tag' represents the HTML tag and 'attr' represents the name of the attribute
# whose value gives the embedded object.
#
# The second form allows to specify the name of a filter attribute 'filter_attr' and
# the value 'filter_value' that it must match for the embedded object to be prefetched.
#
# eg: <img height=10 width=10 src="http://www.example.com/images/1.gif">
# here, tag is "img" and attr is "src"
# so the line would be:
# html_tag img src
#
# eg: <link rel="stylesheet" type="text/css" href="example.css">
# here, tag is "link" and attr is "href"
# an specifying filter_tag as "rel" and filter_value as "stylesheet" enables to
# prefetch only cascading style sheet links.
# so the line would be:
# html_tag link href rel stylesheet

#the following pairs are part of default set of tags used. You could uncomment these and
#add more if necessary:

# html_tag 	img	src
# html_tag 	body 	background
# html_tag 	frame 	src
# html_tag 	fig 	src
# html_tag 	applet 	code
# html_tag 	script 	src
# html_tag 	embed 	src
# html_tag 	td	background