[
https://issues.apache.org/jira/browse/SCB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16507622#comment-16507622
]
ASF GitHub Bot commented on SCB-653:
------------------------------------
coveralls commented on issue #759: [SCB-653]Transfer-Encoding and
Content-Length can not be set to response
URL:
https://github.com/apache/incubator-servicecomb-java-chassis/pull/759#issuecomment-396107524
[](https://coveralls.io/builds/17417919)
Coverage decreased (-0.06%) to 87.396% when pulling
**c6de8cd5045cbc49367d351b24d53a3f3b6a05bf on liubao68:trunked-encoding** into
**45f74522fb7dce719ba09f493530212e4be17860 on apache:master**.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
> When provider returns Transfer-Encoding header and Edge will cause problem
> --------------------------------------------------------------------------
>
> Key: SCB-653
> URL: https://issues.apache.org/jira/browse/SCB-653
> Project: Apache ServiceComb
> Issue Type: Bug
> Reporter: liubao
> Assignee: liubao
> Priority: Major
>
> When provider return Transfer-Encoding, Edge will copy this header to it's
> response, and edge will add Content-Length based on it's on strategy.
> Content-Length & Transfer-Encoding: trunked is conflict features of HTTP.
>
> We need to ignore HTTP internal headers of client response when sending it.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
