Cisco Cisco Packet Data Interworking Function (PDIF)
ACS Ruledef Configuration Mode Commands
▀ http error
▄ Command Line Interface Reference, StarOS Release 17
880
http error
This command allows you to define rule expressions to match for errors in HTTP packets (for example, invalid HTTP
header) and errors in the HTTP analyzer FSM (Finite State Machine) while parsing HTTP packets.
header) and errors in the HTTP analyzer FSM (Finite State Machine) while parsing HTTP packets.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration > Ruledef Configuration
active-charging service service_name > ruledef ruledef_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-acs-ruledef)#
Syntax
[ no ] http error operator condition
no
If previously configured, deletes the specified rule expression from the current ruledef.
operator
Specifies how to match.
operator
must be one of the following:
!=
: Does not equal
=
: Equals
condition
Specifies the condition to match.
condition
must be one of the following:
FALSE
TRUE
Usage
Use this command to define rule expressions to match for errors in HTTP packets and other errors in HTTP
analyzer FSM while parsing HTTP packets. For example, FSM error, invalid header field values, ACS
memory and buffer limit, packet related errors, and so on.
ACS supports pipelining of up to 32 HTTP requests on the same TCP connection. Pipeline overflow requests
are not analyzed. Such overflow requests are treated as HTTP error. The billing system, based on this
information, decides to charge or not charge, or refund the subscriber accordingly.
In 14.0 and later releases, the ECS HTTP analyzer supports both CRLF and LF as valid terminators for HTTP
header fields.
analyzer FSM while parsing HTTP packets. For example, FSM error, invalid header field values, ACS
memory and buffer limit, packet related errors, and so on.
ACS supports pipelining of up to 32 HTTP requests on the same TCP connection. Pipeline overflow requests
are not analyzed. Such overflow requests are treated as HTTP error. The billing system, based on this
information, decides to charge or not charge, or refund the subscriber accordingly.
In 14.0 and later releases, the ECS HTTP analyzer supports both CRLF and LF as valid terminators for HTTP
header fields.
Example
The following command defines a rule expression to match user traffic based on HTTP error status of
TRUE
: