From: armylegionmedic@aol.com
Date: Tue Feb 24 2009 - 14:52:47 ARST
Hello all,
?? In regards to this matching, can someone help me understand the difference between matching based on host and URL in your examples? Say for example, if I want to block the entire site of youtube.com, could I do match protocol http url http://www.youtube.com/* ? Also, on this, if someone just types http://youtube.com will this go through?
Thanks,
James
-----Original Message-----
From: Dale Shaw <dale.shaw@gmail.com>
To: Ivan Walker <ivan@itpro.co.nz>
Cc: olumayokun fowowe <olumayokun@gmail.com>; Jared Scrivener <jscrivener@ipexpert.com>; mahmoud genidy <ccie.mahmoud@gmail.com>; Cisco certification <ccielab@groupstudy.com>
Sent: Mon, 23 Feb 2009 11:56 pm
Subject: Re: QOS with nbar
Ahhh, good work. I never considered the content size to be relevant
but that's very interesting. I also only performed very primitive
tests as I was restricted to a lab with no 'real' HTTP client or
content to shift around.
I might have to revisit 'match protocol http mime' and test with some
larger files. I'm not sure why it would make a difference to IOS
though, since the Content-Type: header can be seen prior to any of the
actual content coming through.
cheers,
Dale
On Tue, Feb 24, 2009 at 6:35 PM, Ivan Walker <ivan@itpro.co.nz> wrote:
> Great testing Dale. Thanks. You beat me to it but I finished my tests
> before I saw your email so here are my results :-) Overall very similar. I
> only tested matching url or mime type and policing or dropping.
Blogs and organic groups at http://www.ccie.net
This archive was generated by hypermail 2.1.4 : Sun Mar 01 2009 - 09:44:12 ARST