[
https://issues.apache.org/jira/browse/TS-1004?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13281436#comment-13281436
]
Otto van der Schaaf commented on TS-1004:
-----------------------------------------
Hi Brian,
Thanks, i'll have a look at this today, and see if i can figure out a proper
way to address this.
My initial thought is, that when the transfer encoding is chunked, the
content-length header field should never be send no matter what.
the specs say something like this about this ambiguous situation / violation
(http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html)
"Messages MUST NOT include both a Content-Length header field and a
non-identity transfer-coding. If the message does include a non- identity
transfer-coding, the Content-Length MUST be ignored."
so, it seems we are lucky on this. but it still needs to be addressed indeed :)
> transformation plugins cause connection close when content length is not
> known ahead
> ------------------------------------------------------------------------------------
>
> Key: TS-1004
> URL: https://issues.apache.org/jira/browse/TS-1004
> Project: Traffic Server
> Issue Type: Bug
> Components: HTTP, Plugins
> Affects Versions: 3.0.1
> Reporter: Otto van der Schaaf
> Assignee: Otto van der Schaaf
> Fix For: 3.1.1, 3.0.3
>
> Attachments: chunk_transform_response.diff
>
>
> whenever the null transform plugin (or gzip) is executed, ATS will force the
> ua connection closed.
> when the user agent supports it, sending a chunked response w/ keepalive
> enabled would be preferred i guess
> i'll add a patch for review.
--
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
