Skip to content

[P2] Preserve the pagination and ETag headers advertised to browser clients #55

Closed

Description

@michielbdejong

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.

Evidence

Desired outcome

Align the forwarding allowlist and browser contract. Add tests that these headers survive forwarding while provider credentials and cookies remain stripped.

Activity

  1. michielbdejong commented on Sep 16, 2026

    @michielbdejong
    ContributorAuthor

    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.


    Generated by Claude Code

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions