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

["Bryan Call (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/TS-464?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15421223#comment-15421223 ] 

Bryan Call commented on TS-464:
-------------------------------

We should remove the content length header if we are chunking and not rely on it.

> Chunked response with bad Content-Length header to HTTP/1.0 client 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
>              Labels: HTTP, Violation, newbie
>             Fix For: sometime
>
>
> 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 was sent by Atlassian JIRA
(v6.3.4#6332)