[
https://issues.apache.org/jira/browse/TS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12915493#action_12915493
]
Leif Hedstrom commented on TS-464:
----------------------------------
And a similar problem with HTTP/1.1 POST requests, that sends both chunked
encoded body and a bad CL header. It looks like we don't send the POST body at
all in this case (i.e. we misinterpret the CL: header, even though it has less
precedence than the chunked encoded entity).
> Chunked response with bad Content-Length header to HTTP/1.0 clent is broken
> ---------------------------------------------------------------------------
>
> Key: TS-464
> URL: https://issues.apache.org/jira/browse/TS-464
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP
> Reporter: Leif Hedstrom
> Fix For: 2.3.0
>
>
> A client sends an HTTP/1.0 request through ATS, which gets proxied with
> HTTP/1.1 to the origin. The origin (which is at fault here, but nonetheless)
> returns with both
> Content-Length: 10
> Transfer-Encoding: chunked
> and a chunked body which is > 10 bytes long. In this case, ATS should still
> respond with an HTTP/1.0 response, undoing the chunking, and return with an
> appropriate CL: header. We do everything, except set the correct
> Content-Length header, we simply return the erroneous CL header that the
> Origin provided. This is not allowed in the RFC.
> (Originally discovered using Coadvisor).
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
