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
Strip all hop-by-hop headers from Lambda responses #66
The Lambda response adapter currently strips Content-Length, Transfer-Encoding, and Connection before copying response headers to the downstream HTTP response.
As Caddy is acting as an HTTP gateway, it should strip the complete set of hop-by-hop headers rather than allowing connection-specific response semantics returned by the Lambda application to propagate to the client.
This should include:
Connection
Proxy-Connection
Keep-Alive
Proxy-Authenticate
Proxy-Authorization
TE
Trailer
Transfer-Encoding
Upgrade
Headers named by the Connection header should also be removed where applicable.
This would bring the response handling closer to the behaviour expected from an HTTP reverse proxy/gateway.
Acceptance criteria
All standard hop-by-hop headers are removed from Lambda responses.
Headers nominated by the Connection header are also removed.
Existing handling of Content-Length is preserved.
Tests cover hop-by-hop header removal.
Normal end-to-end headers continue to pass through unchanged.
Activity
danmoz commentedon Sep 5, 2026
/oc PR please.
opencode-agent commentedon Sep 5, 2026
Created PR #76
opencode session | github run