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)
Sat, Jan 4, 2:57 AM
Unknown Object (File)
Wed, Dec 25, 10:22 PM
Unknown Object (File)
Dec 10 2024, 9:21 PM
Unknown Object (File)
Dec 9 2024, 4:54 PM
Unknown Object (File)
Dec 9 2024, 4:54 PM
Unknown Object (File)
Dec 9 2024, 4:52 PM
Unknown Object (File)
Dec 9 2024, 4:44 PM
Unknown Object (File)
Nov 30 2024, 5:22 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