Revision d82b9cdbc68258faa69598618ec0ff9820f7cf23 authored by Emanuele Rocca on 13 June 2017, 12:53:48 UTC, committed by Ema on 13 June 2017, 15:35:35 UTC
Analytics data indicates that 300/60s should cover the full request load for the worst single client IP we can see in the past week (an MSFT IP, likely a Bing crawler). Moreover, our ratelimiting here only applies to cache miss/pass traffic, not cache hits, further adding lots of headroom for normal cases. To err on the side of caution, exempt seemingly-authenticated requests. Bug: T163233 Change-Id: Icb8ceae901a87ff31005e45d5cd0f2d0f41c6e47
1 parent 003dc00
Computing file changes ...