Bug ID 1004897: 'Decompression' is logged instead of 'Max Headers Exceeded' GoAway reason

Last Modified: Feb 07, 2024

Affected Product(s):
BIG-IP LTM(all modules)

Known Affected Versions:
12.1.6,, 13.1.4,, 13.1.5,, 14.1.0,,,,,, 14.1.2,,,,,,,,, 14.1.3,, 14.1.4,,,, 15.1.0,,,,,, 15.1.1, 15.1.2,, 15.1.3,, 15.1.4,, 15.1.5,, 15.1.6, 16.0.0,, 16.0.1,,

Fixed In:

Opened: Mar 24, 2021

Severity: 3-Major


In HTTP2 setup, when the header count from the client request exceeds max-header-count value in the HTTP profile , COMPRESSION_ERROR(0x09) is seen in GoAway frame instead of FRAME_SIZE_ERROR(0x06)


Wrong GoAway Reason is logged


- Virtual server with HTTP2 enabled - A http2 request has a header count that exceeds 'Maximum Header Count' in the HTTP profile (default value is 64)



Fix Information

When header count in client request exceeds max-header-count value in HTTP profile 1) FRAME_SIZE_ERROR(0x06) error code sent with GoAway frame 2) In http2 profile stats (tmsh show ltm profile http2 all) 'Max Headers Exceeded' is logged as GoAway reason

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips