6 Commits

• 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

  Kirill Turanskiy · 2026-02-18 00:16:22 +03:00
  1f8f198c45
• refactor(all): replace manual pointer assignments with new to enhance code readability and maintainability
  Luis Pater · 2026-02-15 14:10:10 +08:00
  46a6782065
• fix(logging): capture streaming TTFB on first chunk and make timestamps required

  - Add firstChunkTimestamp field to ResponseWriterWrapper for sync capture
  - Capture TTFB in Write() and WriteString() before async channel send
  - Add SetFirstChunkTimestamp() to StreamingLogWriter interface
  - Make requestTimestamp/apiResponseTimestamp required in LogRequest()
  - Remove timestamp capture from WriteAPIResponse() (now via setter)
  - Fix Gemini handler to set API_RESPONSE_TIMESTAMP before writing response
  
  This ensures accurate TTFB measurement for all streaming API formats
  (OpenAI, Gemini, Claude) by capturing timestamp synchronously when
  the first response chunk arrives, not when the stream finalizes.

  sususu98 · 2026-01-29 22:32:24 +08:00
  295f34d7f0
• fix(logging): add API response timestamp and fix request timestamp timing

  Previously:
  - REQUEST INFO timestamp was captured at log write time (not request arrival)
  - API RESPONSE had NO timestamp at all
  
  This fix:
  - Captures REQUEST INFO timestamp when request first arrives
  - Adds API RESPONSE timestamp when upstream response arrives
  
  Changes:
  - Add Timestamp field to RequestInfo, set at middleware initialization
  - Set API_RESPONSE_TIMESTAMP in appendAPIResponse() and gemini handler
  - Pass timestamps through logging chain to writeNonStreamingLog()
  - Add timestamp output to API RESPONSE section
  
  This enables accurate measurement of backend response latency in error logs.

  sususu98 · 2026-01-29 22:22:18 +08:00
  c41ce77eea
• fix: improve streaming bootstrap and forwarding
  gwizz · 2025-12-22 23:34:23 +11:00
  71a6dffbb6
• refactor(config): migrate to SDKConfig and streamline proxy handling

  - Replaced `config.Config` with `config.SDKConfig` across components for simpler configuration management.
  - Updated proxy setup functions and handlers to align with `SDKConfig` improvements.
  - Reorganized handler imports to match new SDK structure.

  Luis Pater · 2025-09-27 04:50:23 +08:00
  57c9ba49f4