You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
More of a feature request than a bug. While checking the status of a processing authorization, Retry-After headers that the server sends are ignored. Instead a fixed 2 second retry interval is used. There is some code in _send_signed_request() to deal with these headers but it's only triggered by an error response.
The RFC doesn't explicitly require clients to obey the header:
7.5.1. Responding to Challenges
...
To check on the status of an authorization, the client sends a POST-
as-GET request to the authorization URL, and the server responds with
the current authorization object. In responding to poll requests
while the validation is still in progress, the server MUST return a
200 (OK) response and MAY include a Retry-After header field to
suggest a polling interval to the client.
But it might be nice. Implementing this would also necessitate a change in the number of max attempts from 30 to something dynamic.
I'd submit a PR but, even as someone pretty familiar with shell scripting, I find this code pretty bewildering.
Debug log
Note the response headers contain a retry-after header, but the retry interval is set to 2 seconds.
Please upgrade to the latest code and try again first. Maybe it's already fixed. acme.sh --upgrade If it's still not working, please provide the log with --debug 2, otherwise, nobody can help you.
More of a feature request than a bug. While checking the status of a processing authorization,
Retry-After
headers that the server sends are ignored. Instead a fixed 2 second retry interval is used. There is some code in_send_signed_request()
to deal with these headers but it's only triggered by an error response.The RFC doesn't explicitly require clients to obey the header:
But it might be nice. Implementing this would also necessitate a change in the number of max attempts from 30 to something dynamic.
I'd submit a PR but, even as someone pretty familiar with shell scripting, I find this code pretty bewildering.
Debug log
Note the response headers contain a retry-after header, but the retry interval is set to 2 seconds.
The text was updated successfully, but these errors were encountered: