Cisco Explorer 4700 Installation Guide Page 448

  • Download
  • Add to my manuals
  • Print
  • Page
    / 648
  • Table of contents
  • TROUBLESHOOTING
  • BOOKMARKS
  • Rated. / 5. Based on customer reviews
Page view 447
12-28
Device Manager Guide, Cisco ACE 4700 Series Application Control Engine Appliance
OL-26645-02
Chapter 12 Configuring Traffic Policies
Setting Match Conditions for Class Maps
Header MIME Type Multipurpose Internet Mail Extension (MIME) message types are to be used for application
inspection decisions.
In the Header MIME Type field, select the MIME message type to use for this match condition.
Port Misuse The misuse of port 80 (or any other port running HTTP) is to be used for application inspection
decisions.
Indicate the application category to use for this match condition:
IM—Indicates that instant messaging applications are to be used for this match condition.
P2P—Indicates that peer-to-peer applications are to be used for this match condition.
Tunneling—Indicates that tunneling applications are to be used for this match condition.
Request Method The request method is to be used for application inspection decisions.
By default, ACE appliances allow all request and extension methods. This option allows you to
configure class maps that define application inspection decisions based on compliance to request
methods defined in RFC 2616 and by HTTP extension methods.
1. In the Request Method Type field, select the type of compliance to be used for application
inspection decision:
Ext—Indicates that an HTTP extension method is to be used for application inspection
decisions.
Note The list of available HTTP extension methods from which to choose varies
depending on the version of software installed in the ACE.
RFC—Indicates that a request method defined in RFC 2616 is to be used for application
inspection decisions.
Depending on your selection, the Ext Request Method field or the RFC Request Method field
appears.
2. In the Request Method field, select the specific request method to be used.
Transfer Encoding An HTTP transfer-encoding type is to be used for application inspection decisions. The
transfer-encoding general-header field indicates the type of transformation, if any, that has been
applied to the HTTP message body to safely transfer it between the sender and the recipient.
In the Transfer Encoding field, select the type of encoding that is to be checked:
Chunked—The message body is transferred as a series of chunks.
Compress—The encoding format that is produced by the UNIX file compression program
compress.
Deflate—The .zlib format that is defined in RFC 1950 in combination with the DEFLATE
compression mechanism described in RFC 1951.
Gzip—The encoding format that is produced by the file compression program GZIP (GNU
zip) as described in RFC 1952.
Identity—The default (identity) encoding which does not require the use of transformation.
Table 12-12 HTTP Protocol Inspection Match Condition Types (continued)
Match Condition Type Description
Page view 447
1 ... 447 448 449 ... 648

Comments to this Manuals

No comments