Files
84e4c62fbd Retry a dropped Dynadot connection (#7)
A full-zone write died with SSL UNEXPECTED_EOF_WHILE_READING. Not our request:
three plain requests to their API from one machine gave 000, 200, 000 within a
few seconds. Their endpoint is simply unreliable, and the operator was being
made the retry loop.

Only a connection that produced no response is retried. An HTTP status is an
answer, however unwelcome, and repeating a request the server already judged
turns one refusal into several.

Retrying a POST is safe here specifically because set_hosts replaces the whole
zone with add_dns_to_current_setting false, so the same body applied twice
leaves the same zone and a reply lost on the way back costs a duplicate write
and nothing else. The comment says plainly that this does not transfer to an
endpoint that appends, and a test pins both halves of that reasoning.

Co-authored-by: jw <jw@jwmacbookm5.local>
2026-08-25 08:50:08 -04:00
..
2026-07-07 09:37:36 -04:00
2026-07-11 11:05:48 -04:00
2026-07-11 11:05:48 -04:00
2026-07-06 07:00:04 -04:00
2026-07-07 09:37:36 -04:00
2026-07-08 10:12:59 -04:00
2026-07-06 18:06:42 -04:00
2026-07-08 09:11:32 -04:00
2026-07-08 10:12:59 -04:00
2026-07-08 10:12:59 -04:00