Cisco Systems OL-15491-01 Network Hardware User Manual


 
A-175
Cisco Content Services Gateway - 2nd Generation Release 2.0 Installation and Configuration Guide
OL-15491-01
Appendix A CSG2 Command Reference
match url
As a further example, by default the following URLs do not match:
http://www.cisco.com/index.html
http://www.cisco.com/INDEX.html
However, if you have disabled case-sensitivity by entering the no ip csg case-sensitive command,
then all of the following URLs match:
http://www.cisco.com/index.html
http://www.cisco.com/INDEX.html
http://www.cisco.com/Index.html
http://www.cisco.com/IndeX.html
http://www.cisco.com/INdex.html
When you configure URL match patterns for Real Time Streaming Protocol (RTSP) streams, be sure
to account for trailing stream IDs in RTSP stream names. For example, URL match pattern *.mpeg
does not match rtsp://1.1.1.254:554/movie.mpeg/streamid=0 because the stream name has a
trailing /streamid=0. To match such RTSP stream names, use a URL match pattern such as
*.mpeg*.
You can include up to two wildcards in each URL match pattern, but the more wildcard matches you
use, the fewer URL maps and URL match patterns the CSG2 can handle, depending on your
configuration. For example, the CSG2 can handle the following combinations of URL maps and
URL match patterns:
If you have one content and 1023 policies, then the CSG2 can handle up to 1023 URL maps,
each with one URL match pattern and no wildcards.
If you have 2000 contents, each with the same policy and the same URL map, then the CSG2
can handle up to 100 URL match patterns for that map, with one wildcard in each pattern (such
as *movies or movies*, but not *movies*).
If you have one content, one policy, and one URL map, then the CSG2 can handle up to 17
match patterns for that map, with two wildcards in each pattern (such as *movies*).
When using wildcards in URL match patterns, observe the following guidelines to optimize the
performance of the CSG2:
Minimize the number of URL match patterns that are applied to a CSG2 content configuration.
Minimize the number of keyword URL match patterns that you use. In general, it is better to use
multiple single-wildcard URL match patterns instead of individual keyword URL match
patterns.
Combine several keyword URL match patterns into a single pattern by using UNIX
string-matching special characters. For example, *.movies_comedy.com/*.mpeg,
*.movies_action.com/*.mpeg, and *.movies_drama.com/*.mpeg can be combined into the
following single pattern:
*.movies_(comedy|action|drama).com/*.mpeg
And these patterns
*.movies_comedy.com/*.mpeg
*.movies_action.com/*.mpeg