Thank you for your reply. I meant 503 service unavailable response to stunnel client's CONNECT request, not to original sender's GET or POST request. I hope that stunnel clients retry CONNECT after 503.
I tried "retry = yes" configuration, but stunnel clients did not work as I had expected. Can I adopt another approach? 2021年9月17日(金) 3:44 Norbert Hanke <[email protected]>: > stunnel acts strictly on the TLS level. It is not aware of the meaning of > the payload that gets moved through the tunnel. No matter if that is HTTP, > LDAP, SMTP, whatever. > > If there is an HTTP 503 response from a server that will end up on the > client as-is. > On 16.09.2021 19:29, Haruka Takagi wrote: > > 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] > > _______________________________________________ > stunnel-users mailing list -- [email protected] > To unsubscribe send an email to [email protected] >
_______________________________________________ stunnel-users mailing list -- [email protected] To unsubscribe send an email to [email protected]
