# عند الوصول إلى حد معدل الطلبات، أعد رأس Retry-After

**URL:** <https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838>\
**Category:** Feature\
**Tags:** pr-welcome\
**Created:** [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:** 3

<div class="post-metadata">

**Author:** ![xrav3nz](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/xrav3nz/32/76894_2.png) [@xrav3nz](https://meta.discourse.org/u/xrav3nz)\
**Post date:** [8 مارس 2018، 3:14ص UTC](https://meta.discourse.org/t/when-rate-limiting-is-hit-return-return-a-retry-after-header/81838/3 "2018-03-08T03:14:15Z")

</div>

Taking a stab at this 😉

* * *

[https://github.com/discourse/discourse/pull/5659](https://github.com/discourse/discourse/pull/5659)

* * *

I am assuming:

`Retry-After` shouldn’t be set in controller actions like the following, where the retry time is (intentionally) hidden from the end user.

[https://github.com/xrav3nz/discourse/blob/60e5f39130ca1e4711400955969990fa283fa969/app/controllers/invites\_controller.rb#L151](https://github.com/xrav3nz/discourse/blob/60e5f39130ca1e4711400955969990fa283fa969/app/controllers/invites_controller.rb#L151)

---

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