Last Modified: Jul 18, 2026
Affected Product(s):
BIG-IP LTM
Known Affected Versions:
11.5.1, 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, 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, 11.5.10, 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, 12.0.0, 12.0.0 hf1, 12.0.0 hf2, 12.0.0 hf3, 12.0.0 hf4, 12.1.0, 12.1.0 hf1, 12.1.0 hf2, 12.1.1, 12.1.1 hf1, 12.1.1 hf2
Fixed In:
13.0.0, 12.1.2
Opened: Jul 22, 2016 Severity: 3-Major
Request-oriented OneConnect load balancing ends when the server returns an error status code.
The client remains connected to the server, and no further load-balancing decisions are made.
OneConnect is enabled and the server responds with a HTTP error status code.
It may be possible to detect the HTTP status code in the response, and manually detach the client-side. To do so, use an iRule similar to the following: when HTTP_RESPONSE { if { [HTTP::status] == 200 } { return } if { [HTTP::status] == 401 } { set auth_header [string tolower [HTTP::header values "WWW-Authenticate"]] if { $auth_header contains "negotiate" || $auth_header contains "ntlm" } { # Connection-oriented auth. System should already be doing the right thing unset auth_header return } unset auth_header } catch { ONECONNECT::detach enable } }. Note: These workarounds should not be used when the backend server is using connection-oriented HTTP authentication (e.g., NTLM or Negotiate authentication).
With OneConnect, the client-side remains detachable when the server-side returns an HTTP error status code.