Files
outline/server
Tom MoorandClaude Opus 5 2beacf9d56 fix: Rate limit response headers and first-request accounting (#13506)
* fix: Rate limit response headers and first-request accounting

Retry-After and RateLimit-Reset are both defined as a whole number of
seconds. Retry-After was sent as a fraction and RateLimit-Reset as a full
date string, neither of which a client can act on.

A route limiter is registered by middleware that runs after the point where
quota is consumed, so the first request to reach a path in each process was
never charged against it. Charge it at registration time instead.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

* test: Cover rate limit headers and first request accounting

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
2026-08-21 20:54:57 -04:00
..
2026-08-16 16:36:13 -04:00
2026-08-15 13:25:10 -04:00
2026-08-15 13:25:10 -04:00
2026-08-15 13:25:10 -04:00