Broken 429 Retry-After header

[mixmix]

Select Topic Area

Bug

Body

This API seems to always return Retry-After: 0 for 429 responses
https://api.npmjs.org/downloads/point/last-week/is-even

Expectation

The Retry-After spec suggests the value should be either

• <delay-seconds>
• <http-date>

While a delay of 0 seconds is valid, I don't think it's what is intended, because it results in no slow-down before retrying . This is clearly an error because retrying after 0 seconds leads straight to another 429 error... with retry-after of 0 seconds!

Please check your logic for this API (and others) and ensure > 0 integer value is returned ❤️

Reproducing

// downloads-query.mjs

async function query (i) {
  const res = await fetch('https://api.npmjs.org/downloads/point/last-week/is-even')

  const stats = {
    queryNumber: i,
    status: res.status,
    headers: res.headers.keys()
      .filter(key => key.match(/^(x-rate|retry)/i))
      .reduce((acc, key) => {
        acc[key] = res.headers.get(key)
        return acc
      }, {}),
  }
  console.log(JSON.stringify(stats, null, 2))
}

const N = 1000
Array(N).fill(query).map((q, i) => q(i))

$ node downloads-query.mjs

Output sample:

{
  "queryNumber": 68,
  "status": 429,
  "headers": {
    "retry-after": "0"
  }
}

Expectation

[github-actions[bot]]

💬 Your Product Feedback Has Been Submitted 🎉

Thank you for taking the time to share your insights with us! Your feedback is invaluable as we build a better GitHub experience for all our users.

Here's what you can expect moving forward ⏩

• Your input will be carefully reviewed and cataloged by members of our product teams. 
  • Due to the high volume of submissions, we may not always be able to provide individual responses.
  • Rest assured, your feedback will help chart our course for product improvements.
• Other users may engage with your post, sharing their own perspectives or experiences. 
• GitHub staff may reach out for further clarification or insight. 
  • We may 'Answer' your discussion if there is a current solution, workaround, or roadmap/changelog post related to the feedback.

Where to look to see what's shipping 👀

• Read the Changelog for real-time updates on the latest GitHub features, enhancements, and calls for feedback.
• Explore our Product Roadmap, which details upcoming major releases and initiatives.

What you can do in the meantime 💻

• Upvote and comment on other user feedback Discussions that resonate with you.
• Add more information at any point! Useful details include: use cases, relevant labels, desired outcomes, and any accompanying screenshots.

As a member of the GitHub community, your participation is essential. While we can't promise that every suggestion will be implemented, we want to emphasize that your feedback is instrumental in guiding our decisions and priorities.

Thank you once again for your contribution to making GitHub even better! We're grateful for your ongoing support and collaboration in shaping the future of our platform. ⭐