[
https://issues.apache.org/jira/browse/SCB-653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16506682#comment-16506682
]
ASF GitHub Bot commented on SCB-653:
------------------------------------
WillemJiang commented on a change in pull request #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#discussion_r194200994
##########
File path: demo/demo-jaxrs/jaxrs-client/src/main/resources/microservice.yaml
##########
@@ -34,12 +34,12 @@ servicecomb:
retryHandler: mycustomhandler
cse:
Review comment:
It's better to use servicecomb instead.
----------------------------------------------------------------
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)
