How to resolve service down event together with informing client this has happened possibly with TCP reset sending from CSS to client?
We have ordinary configuration with two real servers and two content rules for http (L5) and https (L4). When service is dying and is already down, CSS still have flow information in its table. Client who is connected to this service is hanging up waiting for application to time out. New connections are sent to the other live service as expected. Is there a way for CSS to notify client that this has happened, let say via TCP reset packet?
This could be done with "flow-reset-reject" command on content rule, but it is not functioning like expected.
Regards,
Branko
