# When rate limiting is hit return return a Retry-After header

**URL:** <https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838>\
**Category:** Feature\
**Tags:** pr-welcome\
**Created:** [2월 28, 2018, 7:16오후 UTC](https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838 "2018-02-28T19:16:58Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![jdevost](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/jdevost/32/119493_2.png) [@jdevost](https://meta.discourse.org/u/jdevost)\
**Post date:** [2월 28, 2018, 7:16오후 UTC](https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838/1 "2018-02-28T19:16:58Z")

</div>

Hi,

Shouldn’t the delay to wait be in the Response as a Retry-After header?

> **[429 Too Many Requests - HTTP | MDN](https://developer.mozilla.org/en-US/docs/Web/HTTP/Reference/Status/429)**
>
> The HTTP 429 Too Many Requests client error response status code indicates the client has sent too many requests in a given amount of time.
> This mechanism of asking the client to slow down the rate of requests is commonly called "rate limiting".

---

_[View the full topic](https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838)._