Page MenuHomePhabricator

Tweak rate limiting point counts for omnipotent users
ClosedPublic

Authored by epriestley on Oct 14 2017, 3:00 PM.
Tags
None
Referenced Files
Unknown Object (File)
Jul 11 2026, 3:42 AM
Unknown Object (File)
Jul 11 2026, 3:42 AM
Unknown Object (File)
Jul 4 2026, 8:06 AM
Unknown Object (File)
Apr 14 2026, 4:48 AM
Unknown Object (File)
Apr 6 2026, 6:47 PM
Unknown Object (File)
Mar 14 2026, 12:08 AM
Unknown Object (File)
Feb 28 2026, 8:23 PM
Unknown Object (File)
Feb 17 2026, 8:25 PM
Subscribers
None

Details

Summary

Ref T13008. We haven't hit any issues with this, but I can imagine we might in the future.

When one host makes an intracluster request to another host, the $viewer ends up as the omnipotent viewer. This viewer isn't logged in, so they'll currently accumulate rate limit points at a high rate.

Instead, don't give them any points. These requests are always legitimate, and if they originated from a user request, that request should be the one getting rate limited.

Test Plan

Browsed around.

Diff Detail

Repository
rP Phabricator
Lint
Lint Not Applicable
Unit
Tests Not Applicable