Forum Discussion
Mersin_108215
Nimbostratus
May 31, 2012OneConnect and 404s
Hi all,
Per my understanding from a support engineer, OneConnect will tear down a server side connection if a HTTP 404 is seen.
Have others seen this and can confirm?
What is F5's logic behind this? 404s do not mean the server is in an unhealthy state, only that the data requested does not exist.
Thanks in advance - interested in hearing others' thoughts on this.
- hoolio
Cirrostratus
Hi Mersin,when HTTP_RESPONSE { ONECONNECT::reuse enable }
- Mersin_108215
Nimbostratus
Sweet! Thanks much, Aaron. I'll try out the iRule.- rajeshtripathi_
Nimbostratus
Is there any update to this? Is this behaviour still in v12?
Thanks Rajesh
- samstep
Cirrocumulus
So according to F5 support since v11.2 there is a BigDB variable tmm.http.oc.droponerror controlling whether OneConnect will drop the server-side connection if there is a 404 and most other HTTP errors in Response (enabled by default). Posting this on DevCentral so it becomes public knowledge - I could not find documentation about this BigDB entry anywhere in LTM documentation
tmsh show running-config sys db tmm.http.oc.droponerror sys db tmm.http.oc.droponerror { value "true" }
Recent Discussions
Related Content
DevCentral Quicklinks
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com
Discover DevCentral Connects