Retries don't seem to trigger for "Failed to connect to partner using SSL certificate" exceptions #443
|
Hi there, I saw this exception today:
I have resends configured, but they didn't trigger for this exception. Is that expected since it's an SSL handshake failure? |
Replies: 3 comments 2 replies
|
Yes - that matches the current implementation in code. |
|
@uhurusurfa Gotcha, thanks. Is that configurable by any chance? One of the partners I send to does periodic maintenance that causes this exception to be raised. |
|
I will make it configurable and provide in a release in the next week or so.
…On Thu, May 15, 2025 at 6:26 PM mstroming ***@***.***> wrote:
@uhurusurfa <https://github.com/uhurusurfa> Gotcha, thanks. Is that
configurable by any chance? One of the partners I send to does periodic
maintenance that causes this exception to be raised.
—
Reply to this email directly, view it on GitHub
<#443 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ADFWYMQ2VNE4ETO2T7UBA2326TE4LAVCNFSM6AAAAAB5GNHATGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJWGE3TMOA>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
|
@uhurusurfa That's wonderful! Thanks very much! |
|
Release 4.5.0 supports configuring SSL exceptions to enter a resend loop. |
Yes - that matches the current implementation in code.
Only errors that are considered possibly tranasient and worth retrying for like a complete failure to connect (remote end possibly doing a reset or temporarily down) trigger the resend cycle.
An SSL certificate issue is deemed a significant problem that will not be solved by resending without intervention from an administrator to fix the configuration or upload the correct certificate.