6 Commits

Author	SHA1	Message	Date
Kirill Turanskiy	1f8f198c45	feat: passthrough upstream response headers to clients ... CPA previously stripped ALL response headers from upstream AI provider APIs, preventing clients from seeing rate-limit info, request IDs, server-timing and other useful headers. Changes: - Add Headers field to Response and StreamResult structs - Add FilterUpstreamHeaders helper (hop-by-hop + security denylist) - Add WriteUpstreamHeaders helper (respects CPA-set headers) - ExecuteWithAuthManager/ExecuteCountWithAuthManager now return headers - ExecuteStreamWithAuthManager returns headers from initial connection - All 11 provider executors populate Response.Headers - All handler call sites write filtered upstream headers before response Filtered headers (not forwarded): - RFC 7230 hop-by-hop: Connection, Transfer-Encoding, Keep-Alive, etc. - Security: Set-Cookie - CPA-managed: Content-Length, Content-Encoding	2026-02-18 00:16:22 +03:00
hkfires	ecc850bfb7	feat(executor): apply payload rules using requested model	2026-01-23 16:38:41 +08:00
hkfires	82187bffba	feat(gemini-web): Add conversation affinity selector	2025-09-30 12:21:51 +08:00
Luis Pater	f5dc380b63	rebuild branch	2025-09-25 10:32:48 +08:00
Luis Pater	3f69254f43	remove all	2025-09-25 10:31:02 +08:00
Luis Pater	4999fce7f4	v6 version first commit	2025-09-22 01:40:24 +08:00