Tree
- Tree:
2cc4563ecfad9d1e6cbe9aedaa21b02cde36c2be- Date:
- Message:
- relayd: strip Content-Length for chunked messages RFC 9112 section 6.1 requires an intermediary that forwards a message carrying Transfer-Encoding to remove any received Content-Length first. relayd already parses the body as chunked in this case, but previously left Content-Length in the header tree, so the backend could receive both framing fields and choose a different message boundary. When chunked framing is selected, remove Content-Length before header emission; this preserves relayd's chunked body handling while avoiding CL.TE ambiguity downstream. Reproted by: Stuart Thomas OK: rsaodwski@