Bug ID 537704: A false RFC violation happens when there are spaces after the content length header

Last Modified: Nov 07, 2022

Bug Tracker

Affected Product:  See more info
BIG-IP ASM(all modules)

Known Affected Versions:
11.5.1, 11.5.1 HF1, 11.5.1 HF10, 11.5.1 HF11, 11.5.1 HF2, 11.5.1 HF3, 11.5.1 HF4, 11.5.1 HF5, 11.5.1 HF6, 11.5.1 HF7, 11.5.1 HF8, 11.5.1 HF9, 11.5.10, 11.5.2, 11.5.2 HF1, 11.5.3, 11.5.3 HF1, 11.5.3 HF2, 11.5.4, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 11.5.5, 11.5.6, 11.5.7, 11.5.8, 11.5.9, 12.0.0, 12.0.0 HF1, 12.0.0 HF2, 12.0.0 HF3, 12.0.0 HF4

Fixed In:
12.1.0

Opened: Aug 05, 2015
Severity: 3-Major

Symptoms

The system issues a false positive "HTTP protocol compliance failed" sub-violation: "Unparsable request content" if there are spaces after the digits in the content length header.

Impact

A false positive violation

Conditions

Spaces after the digits in the content length header

Workaround

To work around this issue, create an iRule that strips the content length of the trailing spaces.

Fix Information

asm ignores Content length header with trailing whitespaces.

Behavior Change