Skip to content

fix(poller): cap stored Retry-After cooldowns - #135

Merged
CodeZeno merged 1 commit into
mainfrom
fix/cap-stored-retry-after
Sep 24, 2026
Merged

CodeZeno merged 1 commit into
mainfrom
fix/cap-stored-retry-after

Conversation

@CodeZeno

Copy link
Copy Markdown
Owner

Summary

  • Cap stored Retry-After cooldowns so unusually large server-provided delays cannot block provider polling indefinitely.

Testing

  • Regression coverage added for cooldown storage and maximum retry delay handling.

Checklist

  • I have read CONTRIBUTING.md and CODE_OF_CONDUCT.md.
  • The change is focused and contains no credentials or sensitive data.
  • I have added or updated relevant documentation and tests, where applicable.
  • I have left changelog and version changes to maintainers unless requested.

- Bound numeric and HTTP-date cooldowns to one day
- Cover oversized headers and expiry behavior
@CodeZeno
CodeZeno merged commit ad57a6b into main Sep 24, 2026
2 checks passed
CodeZeno added a commit that referenced this pull request Sep 24, 2026
CodeZeno added a commit that referenced this pull request Sep 25, 2026
CodeZeno added a commit that referenced this pull request Sep 25, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant