Bug ID 434557: AAM should call assembler only on cacheable response codes.

Last Modified: Mar 12, 2019

Bug Tracker

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

Known Affected Versions:
11.4.0, 11.4.1, 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.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

Fixed In:
11.5.0

Opened: Oct 18, 2013
Severity: 3-Major
Related AskF5 Article:
K37137992

Symptoms

AAM should call assembler only on configured cacheable response codes and not all. In case of response codes such as 206, the assembler is incorrectly called.

Impact

Assembly is incorrectly called thereby potentially resetting the connection.

Conditions

AAM assembly optimization feature configured and non-cacheable response code is received.

Workaround

None

Fix Information

The received response code is checked against the configured cacheable response codes for making the decision to call AAM assembler.

Behavior Change