From 46d76ecc93e099447f5db053a892334bd6dc83b7 Mon Sep 17 00:00:00 2001 From: Nick Santos Date: Wed, 25 Jun 2025 09:23:06 -0400 Subject: [PATCH] api: fix retry-after header docs Fixes https://github.com/docker/hub-feedback/issues/2459 --- content/reference/api/hub/latest.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/reference/api/hub/latest.yaml b/content/reference/api/hub/latest.yaml index ab325399f640..681870cc93df 100644 --- a/content/reference/api/hub/latest.yaml +++ b/content/reference/api/hub/latest.yaml @@ -40,9 +40,9 @@ tags: - `X-RateLimit-Remaining` - The remaining amount of calls within the limit period. - `X-RateLimit-Reset` - The unix timestamp of when the remaining resets. - If you have hit the limit, you will receive a response status of `429` and the `X-Retry-After` header in the response. + If you have hit the limit, you will receive a response status of `429` and the `Retry-After` header in the response. - The `X-Retry-After` header is a unix timestamp of when you can call the API again. + The [`Retry-After` header](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Headers/Retry-After) specifies the number of seconds to wait until you can call the API again. **Note**: These rate limits are separate from anti-abuse and Docker Hub download, or pull rate limiting. To learn more about Docker Hub pull rate limiting, see [Usage and limits](https://docs.docker.com/docker-hub/usage/).