Hi Anzine321, IIRC, that is the normal browser behavior to try three times. If that arrives client-side and if the pool member is not marked down it will forward those requests server-side, so yeah, if you are not monitoring, this is why you are seeing this behavior.
when client hit 1 time and f5 sends the same hit request 3 times to the server, the team application told to me, is it possible because we dont have check monitor and at the same time when server is not responsive and send 5xx and f5 re send to server ?
Altocumulus
