Bug ID 513865: APM-generated errors cannot be recognized by web application

Last Modified: Nov 22, 2021

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

Fixed In:

Opened: Mar 23, 2015

Severity: 3-Major


If web application sends AJAX request to non-existent domain name or uses URL which is blocked by configuration, it receives error page from APM. But this page is ordinal human-readable HTML page with HTTP status 200. Web application expects some error status and/or error notifications but it receives normal reply. This may lead to errors.


Web application may not work correctly.


AJAX request to non-existent domain name or to blocked resource.



Fix Information

Now it is possible to send HTTP status 503 for responses with APM-generated errors. This behavior is used by most of proxy servers (like Squid) in similar situations and is handled correctly by all web applications. This feature is disabled by default and may be enabled via special option in Access Profile or by setting special environment variable in Access Policy.

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips