It is my understanding that;
stunnel clients give up connecting servers because of HTTP 503 services
unavailable,
tunneling failure causes stunnel clients to notify original senders of
errors,
and original senders acknowledge communication failure and stop program.

I would like stunnel clients to reconnecting servers in cases of 503 and
not to notify original senders of failure, in order that original senders
are unaware of failure and can continue program.

If possible, I want to do this by writing stunnel.conf without modifying
souce codes.

Is this configuration possible?
_______________________________________________
stunnel-users mailing list -- [email protected]
To unsubscribe send an email to [email protected]

Reply via email to