Store ARI info on persistent storage and follow `Retry-After` header

[xlionjuan]

Welcome

• Yes, I've searched similar issues on GitHub and didn't find any.

How do you use lego?

Docker image

Effective version of lego

v4.23.1

Detailed Description

Lego currently didn't store ARI info on persistent storage, so it needs to GET the ARI endpoint every times when the cronjobs runs, makes the Retry-After useless.

[xlionjuan]

A weird ideas come to my mind

Why not add --ari-wait-to-renew-duration 24h with daily timer or 6h + 6h timer?

--ari-wait-to-renew-duration 24h + daily timer sounds great at the the time nearing start, and can perfectly doing the renew at the time that CA wanted.

[ldez]

I don't understand what you are suggesting.

Currently, lego waits until the Retry-After based on ARI information.
I don't see the point of storing the renewal time.

Note: the issue has been triaged as "question" and not "enhancement".

[xlionjuan]

People will using --ari-wait-to-renew-duration(default is 0s) if they know they're using the CA that supports ARI

So, instead running a hourly cronjobs(And requesting ARI info every hour), creating a daily cronjobs+ --ari-wait-to-renew-duration 24h may be the solution when LEGO didn't support storing ARI information for now, it is unlikely that the window will changed at the last 24 hours, if so, change it to "every 6 hours" + --ari-wait-to-renew-duration 6h.

[xlionjuan]

Currently, lego waits until the Retry-After based on ARI information.

How to test this behaviour? Because it will return error if I disconnect the internet.