Skip to content

feat(vibetype): add rate limit - #328

Merged
dargmuesli merged 1 commit into
mainfrom
feat/vibetype/rate-limit
Oct 31, 2026
Merged

dargmuesli merged 1 commit into
mainfrom
feat/vibetype/rate-limit

Conversation

@dargmuesli

Copy link
Copy Markdown
Member

Rate limiting in the app could not tell clients apart in production: all requests reach the reverse proxy through the Cloudflare tunnel, so every client shared the tunnel's address and therefore a single rate limit bucket, which is why it had been disabled. The reverse proxy now limits requests per client using the Cf-Connecting-Ip header, which Cloudflare sets and clients cannot spoof here since the proxy is reachable only through the tunnel. The limit applies in production only, as development has no such header.

@dargmuesli
dargmuesli merged commit ab1667a into main Oct 31, 2026
7 checks passed
@dargmuesli
dargmuesli deleted the feat/vibetype/rate-limit branch October 31, 2026 07:34
maevsi-bot pushed a commit that referenced this pull request Oct 31, 2026
## [21.8.0](21.7.3...21.8.0) (2026-10-31)

### Features

* **vibetype:** add rate limit ([#328](#328)) ([ab1667a](ab1667a))
@maevsi-bot

Copy link
Copy Markdown

🎉 This PR is included in version 21.8.0 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants