For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

Mersin_108215's avatar
Mersin_108215
Icon for Nimbostratus rankNimbostratus
May 31, 2012

OneConnect 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.

 

config
design

4 Replies

  • hoolio's avatar
    hoolio
    Icon for Cirrostratus rankCirrostratus
    May 31, 2012
    Hi Mersin,

    Yes, OneConnect disconnects the serverside connection for a 404 response. This is noted in bz365822. I'm not sure what the logic is for this, but you can work around it by using a simple iRule: 

    
when HTTP_RESPONSE {
   ONECONNECT::reuse enable
}

    You could request that the logic be improved in a Support case.

    Aaron
    • rajeshtripathi_'s avatar
      rajeshtripathi_
      Icon for Nimbostratus rankNimbostratus
      Sep 19, 2016

      Is there any update to this? Is this behaviour still in v12?

       

      Thanks Rajesh

       

  • samstep's avatar
    samstep
    Icon for Cirrocumulus rankCirrocumulus
    Sep 21, 2016

    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"
}