[kmcginnes]

Summary

Anyone who can reach the proxy can write to the log, so /logger needs a bound on how fast entries arrive.

User-facing: none

POST /logger
  415 if Content-Type is present and not JSON   (spends no budget)
  429 if more than 300 requests in the window   (answered directly, nothing logged)
  400 / 200 as before

• createRateLimiter is a small fixed-window limiter in rate-limiter.ts, one per app.
• The limit is 300 requests a minute across all callers, and invalid requests count.

Evidence

Before: no limit on request volume.
After: the 301st request in a window gets a 429 and writes no log entry at any level. The window rolls over at exactly 60 seconds, and rejected form posts don't use up the budget.

Merge Danger

Door: two-way

Impact: consumers

A caller sending more than 300 log requests in a minute gets 429s.

Related

• Closes Improve client-to-server logging endpoint #1635

[kmcginnes]

Dropping the rate limiter: the 10,000-character cap already bounds each entry, and Graph Explorer is the only caller.