From: Huan Pham (pnhuan@yahoo.com)
Date: Sat Nov 08 2008 - 10:16:34 ARST
Hi Artur,
This is correct. You need to match statements.
From the router perspective, the website "URL" we normally use consist of two
parts: a host part (server dns), and URL that follows. You can not match URL
with only one single statement.
The best to understand this stuff is to lab it yourself. Try to match the
whole URL and see how the router behaves. I am pretty sure that if you try to
put the whole URL (including the host part) the router will not match
anything!
As a side note, I used to believe that the "match URL" only matches the HTTP
requests from clients to the server, but this statement in fact can match
traffic from server to client as well. I cannot find any docs that explain
this behavior clearly. I only come to this conclusion through playing arround
with routers. Great if someone can shed some more light (to prove this
observation right or wrong).
--- On Sat, 11/8/08, Artur Sant'Anna <artur.lists@gmail.com> wrote:
From: Artur Sant'Anna <artur.lists@gmail.com>
Subject: NBAR Question
To: ccielab@groupstudy.com
Date: Saturday, November 8, 2008, 6:08 AM
Hi there,
After reading the IE Blog about Nbar matching on MQC, I was wondering a
possibility of matching www.cisco.com/univercd
Following their information, would be necessary two statements, one matching
the host part, similar to: match protocol http host www.cisco.com and
another one like: match protocol url /univercd
Is there another way of matching this url using just one line? Is the
information above correct?
Thanks!
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Mon Dec 01 2008 - 08:18:29 ARST