# Rate limiting with h2

**URL:** <https://discourse.haproxy.org/t/rate-limiting-with-h2/2823>\
**Category:** Help!\
**Created:** [August 6, 2018, 8:37am UTC](https://discourse.haproxy.org/t/rate-limiting-with-h2/2823 "2018-08-06T08:37:14Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![peterlh](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@peterlh](https://discourse.haproxy.org/u/peterlh)\
**Post date:** [August 6, 2018, 8:37am UTC](https://discourse.haproxy.org/t/rate-limiting-with-h2/2823/1 "2018-08-06T08:37:15Z")

</div>

Hi all,

We’re been using these rate limiting techniques a long time:

> <https://gist.github.com/jeremyj/e964a951634f1997daea>

But just today noticed, that these apply to connections not to multiplexed h2 connections - as this will allow a run-away-browser to make unlimited amounts of calls to our backend thru h2.

- Is it possible?
- Does anyone have configurations with rate limiting on h2 protocol?

Thanks

---

<div class="post-metadata">

**Author:** ![mrmoroniv](https://avatars.discourse-cdn.com/v4/letter/m/ee59a6/32.png) [@mrmoroniv](https://discourse.haproxy.org/u/mrmoroniv)\
**Post date:** [September 6, 2019, 12:46pm UTC](https://discourse.haproxy.org/t/rate-limiting-with-h2/2823/2 "2019-09-06T12:46:32Z")

</div>

have you ever figured this out?

---

<div class="post-metadata">

**Author:** ![peterlh](https://avatars.discourse-cdn.com/v4/letter/p/eb9ed0/32.png) [@peterlh](https://discourse.haproxy.org/u/peterlh)\
**Post date:** [September 6, 2019, 2:39pm UTC](https://discourse.haproxy.org/t/rate-limiting-with-h2/2823/3 "2019-09-06T14:39:04Z")

</div>

Sadly not.

But iam very interessted if anyone has feedback or hints on how to get similar feature back.