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

Paul_Zajicek_73's avatar
Paul_Zajicek_73
Icon for Nimbostratus rankNimbostratus
May 01, 2018

Not seeing all http 500 responses

Sometimes our web servers receive repeated duplicated requests from a browser within a few seconds, the web server responds ok for the first few, then it generates 500 errors and these are returned t...
application delivery
iRules
youssef1's avatar
youssef1
Icon for Cumulonimbus rankCumulonimbus
May 02, 2018

Hello,

 

To follow up our exchange, as you know HTTP_RESPONSE occurs on every HTTP response. That's mean that is the first event that will be trigged after an response from the backend. https://devcentral.f5.com/questions/irule-event-order-http

 

that's why I'm pretty surprised that your irule don't trigged.

 

to get an answer, we need a request. So Just for testing, you can log all request response and generate this behaviour. Then check if you have an request without response (this would potentially be the 500 error that is not logged).

 

If we see that the problem starts again and all request have it response, it will be another problem (duplicate log entry at the application level)...

 

otherwise if we want to be more precise it will be necessary to make a capture on the application and or F5 (TCPDUMP/wireshark)