# Icon deprecation warnings causing rate limiting issues

**URL:** <https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586>\
**Category:** Product Support\
**Created:** [March 25, 2020, 7:46pm UTC](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586 "2020-03-25T19:46:17Z")\
**Posts on this page:** 1\
**Showing post:** 1

<div class="post-metadata">

**Author:** ![RGJ](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/rgj/32/523185_2.png) [@RGJ](https://meta.discourse.org/u/RGJ)\
**Post date:** [March 25, 2020, 7:46pm UTC](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586/1 "2020-03-25T19:46:17Z")

</div>

We’re seeing more and more of this lately:

Themes and plugins are causing lots of “FA icon deprecation” warnings:

 ![image](https://global.discourse-cdn.com/meta/original/3X/b/3/b39bd281d841eeebe3d3baa0f4034dd7b875317d.png)

and I have seen two different kind of responses to this: “don’t worry it’s just a warning” and “if you want to get rid of them, just fix the theme or plugin” (which is not always easy).

So, let’s just ignore those warnings. Or… as it turns out… these warnings are frequently causing 429 rate limit errors and our logs are full of

 ![image](https://global.discourse-cdn.com/meta/original/3X/8/1/81397d1117787169aed8dce4b050b314a8d8c1a1.png)

Would it be possible to well, rate limit those warnings on the client, so they don’t trigger all those requests? Or exempt `POST /logs/` from rate limiting?

Tagging @outofthebox @WorldIsMine

---

_[View the full topic](https://meta.discourse.org/t/icon-deprecation-warnings-causing-rate-limiting-issues/145586)._
