Cisco Systems OL-15491-01 appendix character, 169

Appendix A CSG2 Command Reference

match header

Convention	Description
\character	Escaped character.
	Examples:
	\?	Match on a question mark (\<ctrl-v>?)
	\+	Match on a plus sign
	\*	Match on an asterisk
	\a	Alert (ASCII 7)
	\b	Backspace (ASCII 8)
	\f	Form-feed (ASCII 12)
	\n	New line (ASCII 10)
	\r	Carriage return (ASCII 13)
	\t	Tab (ASCII 9)
	\v	Vertical tab (ASCC 11)
	\0	Null (ASCII 0)
	\\	Back slash
Bracketed range [0-9]	Matching any single character from the range.
A leading ^ in a range	Do not match any in the range. All other characters represent themselves.
.\x##	Any ASCII character as specified in two-digit hex notation.
	For example, \x3f yields a ? for a one-character wild card match.

When configuring a map, keep the following considerations in mind:

•You cannot specify different types of match patterns in a given map. For example, a map can include one or more match header statements, but it cannot include both match header statements and match url statements.

•You can specify up to three maps in a given policy: one for header matching, one for method matching, and one for URL matching. For example, the following is a valid configuration:

ip csg map HOSTMAP

match header host1 value *.2.*.44

!

ip csg map URLMAP

match url */mobile/index.wml

		!
		ip csg policy MAP-POLICY
		map HOSTMAP
		map URLMAP
		In this example, a flow must match both HOSTMAP and URLMAP in order to match policy
		MAP-POLICY.
Examples		The following example shows how to specify HTTP header match patterns for map HDR1. In this
		example, the header match is TRUE only for host www.cisco.com and user agent myagent. Any other
		combination of host and IP address matches FALSE:
		ip csg map HDR1
		match header Host www.cisco.com
		Cisco Content Services Gateway - 2nd Generation Release 2.0 Installation and Configuration Guide
	OL-15491-01		A-169