Forum Discussion

Altostratus

Dec 01, 2017

SERVER_CONNECTED and reject - how affects clientside

Hi, From my test when I use reject in SERVER_CONNECTED event then following sequence of events is triggered (hope that logging indicates order of events): LB_FAILED CLIENT_CLOSED SERVER_...

Nimbostratus

Dec 01, 2017

Client initiate the URL and destined to F5 and as per your comments if "Server SSL profile not available in corresponding VS" thereafter sending reset packet to server and client from F5 by using reject command, in this scenario no need worry about HTTP::respond. And hope can ignore LB_FAILED, TCP::close.

dragonflymr
Cirrostratus
Dec 01, 2017
Because this is all about HTTP communication and being a bit more polite for client using browser, I do not like to just generate TCP session reset - I would like to inform client about some issues with accessed site via HTTP response codes.

Second reason is that when TCP connection is reset/closed browser is trying to send request few times in a row - at least Firefox seems so. This is overhead so I would like to avoid it. When instead of TCP reset 403 or 500 is returned browser is not trying to send more request.

Piotr