Bug ID 741248: ANTIFRAUD::disable may stall the connection

Last Modified: Jan 20, 2023

Bug Tracker

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

Known Affected Versions:
13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 14.1.4.4, 14.1.4.5, 14.1.4.6, 14.1.5, 14.1.5.1, 14.1.5.2, 14.1.5.3

Fixed In:
15.0.0

Opened: Aug 21, 2018
Severity: 3-Major

Symptoms

ANTIFRAUD::disable may stall the connection if FPS self-responds to the first request (FPS fictive URL).

Impact

Connection is stalled.

Conditions

-- ANTIFRAUD::disable is called for a request that follows a request for which FPS self-responds (a fictive URL: js engine, js config, etc.). -- The fictive request was the first request on this connection. -- Connection is keep-alive.

Workaround

Use the following iRule: when HTTP_REQUEST { set URI [HTTP::path] if { URI eq "<DISABLE_URL>"} { ANTIFRAUD::disable } } when HTTP_RESPONSE_RELEASE { if { $URI eq "<FICTIVE_URL>" } { HTTP::close } }

Fix Information

FPS closes the connection in case FPS responds to the client directly and the corresponding request is the first one on the connection.

Behavior Change