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

Last Modified: Jul 18, 2026

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

Known Affected Versions:
11.6.0, 11.6.0 hf1, 11.6.0 hf2, 11.6.0 hf3, 11.6.0 hf4, 11.6.0 hf5, 11.6.0 hf6, 11.6.0 hf7, 11.6.0 hf8, 11.6.1, 11.6.1 hf1, 11.6.1 hf2, 11.6.2, 11.6.2 hf1, 11.6.3, 11.6.3.1, 11.6.3.2, 11.6.3.3, 11.6.3.4, 11.6.4, 11.6.5, 11.6.5.1, 11.6.5.2, 11.6.5.3

Fixed In:
12.0.0

Opened: Mar 23, 2015

Severity: 3-Major

Symptoms

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.

Impact

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

Conditions

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

Workaround

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