Skip to content

Fix rate limiting behind reverse proxy#4004

Merged
timfrazee merged 4 commits intodocker/digital-oceanfrom
tf/fix-do-rate-limiting
Mar 18, 2026
Merged

Fix rate limiting behind reverse proxy#4004
timfrazee merged 4 commits intodocker/digital-oceanfrom
tf/fix-do-rate-limiting

Conversation

@timfrazee
Copy link
Contributor

@timfrazee timfrazee commented Mar 18, 2026

  • Addresses an issue where requests routed through reverse proxies / load balancers were being aggressively throttled due to obscured client IP addresses
  • Changes throttled request response code to 429 (from 503)
  • Duplicates health check endpoint under /api namespace so it's available when proxied or routed based on request path.

@timfrazee timfrazee force-pushed the tf/fix-do-rate-limiting branch from 9518c57 to d45940d Compare March 18, 2026 21:01
Allows it to be available to API instances proxied behind /api
Addresses an issue where requests routed through reverse proxies / load balancers were being aggressively throttled due to obscured client IP addresses
@timfrazee timfrazee force-pushed the tf/fix-do-rate-limiting branch from d45940d to 49d5be5 Compare March 18, 2026 21:03
@timfrazee timfrazee merged commit 841dd77 into docker/digital-ocean Mar 18, 2026
3 checks passed
@timfrazee timfrazee deleted the tf/fix-do-rate-limiting branch March 18, 2026 21:53
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant