Bug ID 513822: ASM REST: Expected Content Value Is Not Set When Setting The responseActionType For A Response Page

Last Modified: Sep 13, 2023

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

Known Affected Versions:
11.5.1 HF1, 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.1 HF10, 11.5.1 HF11, 11.5.2 HF1, 11.5.3 HF1, 11.5.3 HF2, 11.5.4 HF1, 11.5.4 HF2, 11.5.4 HF3, 11.5.4 HF4, 12.1.0 HF1, 12.1.0 HF2, 12.1.1 HF1, 12.1.1 HF2, 12.1.2 HF1, 12.1.2 HF2

Fixed In:
12.0.0, 11.6.0 HF6

Opened: Mar 23, 2015

Severity: 3-Major


When setting the responseActionType, such as "default" or "soap-fault", to a value that has an expected related unmodifiable responseContent value, the expected responseContent is not set. As a result an empty response page is returned when ASM blocks a request.


An empty response page is returned when ASM blocks a request.


Via ASM REST a client changes the responseActionType from "custom" to "default" or "soap-fault".


The alternate response body can be set explicitly via REST

Fix Information

Expected responseContent is now set when changing responseActionType to a static content type like "default" or "soap-fault" using ASM REST.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips