---
title: "Comment by Ann Baum on \"Rate Limiting Supabase Requests with PostgreSQL and pg_headerkit\" | Hashnode"
description: "This is great – we just implemented rate limiting pretty much exactly as described here. Only small gotcha was the check_rate_limit() function – we forgot that"
url: "https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/66c743aa1b6225a7d840afed"
---

[Discussion](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22)

Comment [Rate Limiting Supabase Requests with PostgreSQL and pg\_headerkit](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22)

[Ann Baum](https://hashnode.com/@anngbaum)

[Aug 22, 2024](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/66c743aa1b6225a7d840afed)

This is great – we just implemented rate limiting pretty much exactly as described here.

Only small gotcha was the check\_rate\_limit() function – we forgot that we use HEAD requests to validate username availability during signup, important to exclude those in addition to GET!

[Rodrigo Mansueli](https://hashnode.com/@mansueli)

[Aug 22, 2024](https://hashnode.com/posts/rate-limiting-supabase-requests-with-postgresql-and-pgheaderkit/64f717aafee4891c8d66ce22/comment/66c743aa1b6225a7d840afed#reply-66c74d89ed8ebfeb1d3622bc)

Thanks for the feedback, Ann. Great to see you here!

I'll update the article to include HEAD there.
