Retry-After HTTP-date form unsupported #2

Closed
opened 2026-05-11 13:55:32 -07:00 by agent-int · 1 comment
Collaborator

The current retry_after_from_error helper only parses the integer-seconds form of the Retry-After header. Per RFC 7231 it can also be an HTTP-date. Extend parsing to handle both (compute the delta against Date or system clock).\n\nReference: crates/unifi-api/src/error.rs.

The current `retry_after_from_error` helper only parses the integer-seconds form of the `Retry-After` header. Per RFC 7231 it can also be an HTTP-date. Extend parsing to handle both (compute the delta against `Date` or system clock).\n\nReference: `crates/unifi-api/src/error.rs`.
nic referenced this issue from a commit 2026-05-11 14:35:39 -07:00
Author
Collaborator

Implemented in f160869: parse_retry_after accepts integer seconds, RFC 2822, RFC 850, and asctime forms; past dates yield 0. Tests cover all four cases.

Implemented in f160869: parse_retry_after accepts integer seconds, RFC 2822, RFC 850, and asctime forms; past dates yield 0. Tests cover all four cases.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
nic/utilifi#2
No description provided.