Skip to content

Clarify potentially confusing Retry-After value #1385

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

Merged
merged 1 commit into from
Apr 2, 2022

Conversation

danielcompton
Copy link
Contributor

The description for this http request talked about retrying sooner than 1 second with Retry-After: 0. Using a Retry-After value of 1 was slightly confusing, as it wasn't clear if this was a typo, or
demonstrating the general retry case.

This commit changes Retry-After to 10 seconds to clearly delineate it from the 0s-1s range.

The description for this http request talked about retrying sooner than 
1 second with Retry-After: 0. Using a Retry-After value of 1 was 
slightly confusing, as it wasn't clear if this was a typo, or
demonstrating the general retry case.

This commit changes Retry-After to 10 seconds to clearly delineate it
from the 0s-1s range.
@dgeb dgeb merged commit 40e51f8 into json-api:gh-pages Apr 2, 2022
@dgeb
Copy link
Member

dgeb commented Apr 2, 2022

Apologies for the delayed response, @danielcompton. Thanks for the clarifying contribution.

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.

3 participants
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy