RE: match protocol http [ url vs mime ]

From: Scott Morris (swm@emanon.com)
Date: Thu Nov 11 2004 - 16:32:36 GMT-3


The protocol type represents a field within the HTTP structures... It will
never look like "*.jpeg". That's a filename call, and within the URL.

MIME types are "image/jpeg", "image/gif", "video/avi" and things like
that... There's an RFC about Multimedia Independent Mail Extensions (MIME),
but I don't recall what its number is...

Otherwise, take a look at your File Associations table in Windows and you'll
have an idea for different MIME types and their name.

HTH,

 
Scott Morris, MCSE, CCDP, CCIE4 (R&S/ISP-Dial/Security/Service Provider)
#4713, JNCIP, CCNA-WAN Switching, CCSP, Cable Communications Specialist, IP
Telephony Support Specialist, IP Telephony Design Specialist, CISSP
CCSI #21903
swm@emanon.com
 
 
 

-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
ccie2be
Sent: Thursday, November 11, 2004 12:31 PM
To: Group Study
Subject: match protocol http [ url vs mime ]

Hi guys,

I need some help figuring out when to use the "mime" parameter when matching
traffic.

For example, if I want to apply a policy which filters or restricts traffic
that contains jpeg files which config should I use?

class-map jpeg
  match protocol http url "*.jpeg"

or

  match protocol http mime "*.jpeg"

Also, can regular expressions be used within the quote marks?

For example, is this OK?

match prot http mime "*.jpeg | *.jpg | *.mpeg"

Any insight or help is greatly appreciated.

TIA, Tim



This archive was generated by hypermail 2.1.4 : Thu Dec 02 2004 - 06:57:42 GMT-3