[jira] [Assigned] (TS-464) Chunked response with bad Content-Length header to HTTP/1.0 clent is broken

["Zhao Yongming (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/TS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Zhao Yongming reassigned TS-464:
--------------------------------

    Assignee: weijin

I think this is the samve issue we are tracking in taobao, where it will case many http SM hangup in system, it never time out and close, it is very dangerous in heavy system like us, Wei jin and Koutai working on this and have a patch for testing currently, will submit it later.
                
> 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
>            Assignee: weijin
>             Fix For: 3.3.1
>
>
> 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.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira