14-20

User

Guide

for

the

Cisco

Application

Networking

Manager

5.2

OL-26572-01

Chapter

14

Configuring

Traffic

Policies

Setting

Match

Conditions

for

Class

Maps

Header

MIME

Type

Multipurpose

Internet

Mail

Extension

(MIME)

message

types

that

are

to

be

used

for

protocol

inspection

decisions.

In

the

Header

MIME

Type

field,

choose

the

MI

ME

message

t

ype

to

use

for

this

match

condition.

Port

Misuse

Feature

that

specifies

that

the

misuse

of

port

80

(or

any

other

port

running

HTTP)

is

to

be

used

for

protocol

inspection

decisions.

Choose

the

application

category

to

use

for

this

match

condition:

•

IM—Instant

messaging

applications

ar

e

to

be

used

for

this

match

condition.

•

P2P—Peer-to-peer

applications

are

to

be

used

for

this

match

condition.

•

Tunneling—Tunneling

applications

are

to

be

used

for

this

match

condition.

Request

Method

Request

method

that

is

to

be

used

for

protocol

inspection

decisions.

By

default,

ACEs

allow

all

request

and

extension

methods.

This

option

allows

you

to

configure

class

maps

that

define

protocol

inspection

decisions

based

on

compliance

to

request

methods

defined

in

RFC

2616

and

by

HTTP

extension

methods.

Do

the

following:

a.

In

the

Request

Method

Type

field,

choose

the

type

of

compliance

to

be

used

for

protocol

inspection

decision.

Choices

are

as

follows:

–

Ext—HTTP

extension

method

is

to

be

used

for

protocol

inspection

decisions.

–

RFC—Request

method

defined

in

RFC

2616

is

to

be

used

for

protocol

inspection

decisions.

Depending

on

your

selection,

the

Ext

Request

Method

field

or

the

RFC

Request

Method

field

appears.

b.

In

the

Request

Method

field,

choose

the

specific

request

method

to

be

used.

Transfer

Encoding

Field

that

appears

when

an

HTTP

transfer-encoding

type

is

used

for

protocol

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,

choose

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

195

0

in

combination

with

t

he

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.

URL

URL

name

used

for

protocol

inspection

decisions.

In

the

URL

field,

enter

a

URL

or

a

portion

of

a

URL

to

match.

Valid

entries

are

URL

strings

from

1

to

255

alphanumeric

characters

and

include

only

the

portion

of

the

URL

following

www.hostname.

domain.

For

example,

in

the

URL

www.anydomain.com/latest/whatsnew.html,

include

only

/latest/whatsnew.html.

Table

14-7

Layer

7

HTTP

Deep

Packet

Inspection

Class

Map

Match

Conditions

(continued)

Match

Condition

Description