``` // Not recommended: many users may share a single IP, especially on mobile networks // or when

// Not recommended:  many users may share a single IP, especially on mobile networks
// or when using privacy-enabling proxies
const ipAddress = req.headers.get("cf-connecting-ip") || ""
const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })

// Not recommended:  many users may share a single IP, especially on mobile networks
// or when using privacy-enabling proxies
const ipAddress = req.headers.get("cf-connecting-ip") || ""
const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })

// Not recommended:  many users may share a single IP, especially on mobile networks
// or when using privacy-enabling proxies
const ipAddress = req.headers.get("cf-connecting-ip") || ""
const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })

// Not recommended:  many users may share a single IP, especially on mobile networks
// or when using privacy-enabling proxies
const ipAddress = req.headers.get("cf-connecting-ip") || ""
const { success } = await env.MY_RATE_LIMITER.limit({ key: ipAddress })

this is from https://developers.cloudflare.com/workers/runtime-apis/bindings/rate-limit/

if users may share a single ip from cf-connecting-ip then how would i handle rate limiting in my actual backend for unauthenticated users? I use cf-connecting-ip with it but does that mean my own backend (not cf worker - I use Laravel) would also block other unauthenticated users that use the same ip even if they are not the culprit?

Cloudflare Docs

Rate Limiting · Cloudflare Workers docs

Define rate limits and interact with them directly from your Cloudflare Worker

``` // Not recommended: many users may share a single IP, especially on mobile networks // or when

Similar Threads

Similar Threads

Similar Threads