You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[P2] Preserve the pagination and ETag headers advertised to browser clients #55
Recorded during review of main at a1eb305ccfa2f3fc8ddede4875765cf1b099bd2b. This issue records a finding only; no implementation changes were made or requested.
Finding
CORS exposes ETag, X-Total-Count, and X-Next-Page, but the proxy response-header filter preserves only Content-Type, Link, and Retry-After. Browser consumers cannot receive the discarded concurrency/pagination metadata, despite its advertised exposure.
Align the forwarding allowlist and browser contract. Add tests that these headers survive forwarding while provider credentials and cookies remain stripped.
Fixed in #73 — ETag, X-Total-Count, and X-Next-Page are now forwarded from the upstream response, matching what CORS already exposes to browser clients.
Activity
michielbdejong commentedon Sep 16, 2026
Fixed in #73 —
ETag,X-Total-Count, andX-Next-Pageare now forwarded from the upstream response, matching what CORS already exposes to browser clients.Generated by Claude Code