Cisco Cisco Packet Data Interworking Function (PDIF)
ACS Rulebase Configuration Mode Commands
▀ http header-parse-limit
▄ Command Line Interface Reference, StarOS Release 17
730
http header-parse-limit
This command allows you to configure the HTTP header parse limit, on exceeding which the flow is marked as
permanent failure and is matched and charged against
permanent failure and is matched and charged against
http error = TRUE
ruledef.
Important:
This command is customer specific. For more information contact your Cisco account representative.
Product
ACS
Privilege
Security Administrator, Administrator
Mode
Exec > ACS Configuration > Rulebase Configuration
active-charging service service_name > rulebase rulebase_name
Entering the above command sequence results in the following prompt:
[local]host_name(config-rule-base)#
Syntax
http header-parse-limit parse_limit_bytes
{ default | no } http header-parse-limit
default
Configures the default setting for this command.
Default: 12000 bytes
Default: 12000 bytes
no
If enabled, disables the header-parse-limit configuration in the current rulebase.
Important:
Disabling header parse limit may lead to uncharged bytes (due to no rule-matching until header is
complete) if header is not correctly terminated.
parse_limit_bytes
Specifies the header-parse-limit, number of bytes.
parse_limit_bytes
must be an integer from 1 through 256000.
Usage
If a user sends HTTP LF terminated traffic instead of the usual HTTP CRLF terminated traffic, and similarly
the server is responding with LF terminated traffic, the traffic does not result in any rule match, and rule
match happens only at flow idle or at call clear when the quota for the same is not requested/updated. This
results in a revenue hole for prepaid subscribers.
the server is responding with LF terminated traffic, the traffic does not result in any rule match, and rule
match happens only at flow idle or at call clear when the quota for the same is not requested/updated. This
results in a revenue hole for prepaid subscribers.