You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Igor Galić (JIRA)" <ji...@apache.org> on 2013/07/11 15:51:49 UTC

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

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

Igor Galić updated TS-464:
--------------------------

    Labels: HTTP Violation  (was: )
    
> 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
>              Labels: HTTP, Violation
>             Fix For: 3.5.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.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira