xia-chao updated PR #15047.
xia-chao edited PR #15047.
xia-chao updated PR #15047.
xia-chao commented on PR #15047:
also updated the two forward_duplicate_content_length tests - they depended on fetching a TE+CL response, which the client rejects now.
xia-chao updated PR #15047.
xia-chao deleted a comment on PR #15047:
also updated the two forward_duplicate_content_length tests - they depended on fetching a TE+CL response, which the client rejects now.
xia-chao commented on PR #15047:
your forward_duplicate_content_length tests from #15070 kind of got in the way here - they relied on a TE+CL response, which the client rejects now.
xia-chao deleted a comment on PR #15047:
your forward_duplicate_content_length tests from #15070 kind of got in the way here - they relied on a TE+CL response, which the client rejects now.
xia-chao commented on PR #15047:
@pchickey your forward_duplicate_content_length tests from #15070 broke here, they relied on a TE+CL response, and the client rejects that now. So I had to update them.
xia-chao updated PR #15047.
xia-chao deleted a comment on PR #15047:
@pchickey your forward_duplicate_content_length tests from #15070 broke here, they relied on a TE+CL response, and the client rejects that now. So I had to update them.
xia-chao edited PR #15047:
Requests and responses that carry both transfer-encoding and content-length are rejected before they reach the guest: 400 for a request and an HttpProtocolError for a response.
Hyper passes both headers through, so a guest was getting a content-length that did not match the body it read.
xia-chao commented on PR #15047:
the duplicate content length tests relied on a TE+CL response, so i changed the fixture
Last updated: Oct 31 2026 at 23:03 UTC