Skip to content

Make it easier to generate Retry-After headers #482

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
jvanasco opened this issue Feb 3, 2025 · 0 comments
Open

Make it easier to generate Retry-After headers #482

jvanasco opened this issue Feb 3, 2025 · 0 comments

Comments

@jvanasco
Copy link
Contributor

jvanasco commented Feb 3, 2025

I could be reading the docs and code wrong, but it seems the only way to generate "retry-after" headers for polling is by actually validating and using the sleep vars; i.e. this implies it is impossible to generate these headers with PEBBLE_VA_ALWAYS_VALID=1 or PEBBLE_AUTHZREUSE=100, which complicates the testing environment needed to ensure the header values are respected.

It would be nice if a PEBBLE_XXX variable could be used in conjunction with the above commands to somehow generate the retry-after headers. Perhaps a flag could just simply stall these authorizations for X seconds before transitioning to valid; or even if there is something that could give every endpoint/request an X seconds retry-after response on a first access - then a Client Author could spin up a "retry" version of pebble to ensure the throttles are being properly respected.

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

No branches or pull requests

1 participant