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

Ravindra's avatar
Ravindra
Icon for Nimbostratus rankNimbostratus
Sep 27, 2017

NGINX http code 499 equivalent in F5

Hi Team, I am working on a migration from NGINX to F5 LTM. As per customer, they get http code 499 on nginx whenever a client closes the connection before backend server process it or send response. ...
application delivery
LTM
TMOS
Lee_Sutcliffe's avatar
Lee_Sutcliffe
Icon for Nacreous rankNacreous
Sep 27, 2017

F5 is a full TCP proxy, so by default will only forward status codes as sent by the backend servers/pool members. You can of course modify these or create custom status codes with an iRule dependent on your requirements

 

For example:

 

when HTTP_REQUEST {
    if {YOUR-CLIENT-CLOSE-CONDITION} {
        HTTP::respond "499" -version 1.1 content "Some Content" 
    }
}

In your case you could read the client close on HTTP_REQUEST and respond with the desired status code. As this is on HTTP_REQUEST, it will respond with the defined status code and bypass load balancing to the backend server.

 

https://devcentral.f5.com/wiki/iRules.HTTP__respond.ashx