Loading...
Loading...
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.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.