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

Posted to issues@servicecomb.apache.org by "liubao (JIRA)" <ji...@apache.org> on 2018/06/11 08:31:00 UTC

[jira] [Closed] (SCB-653) When provider returns Transfer-Encoding header and Edge will cause problem

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

liubao closed SCB-653.
----------------------
    Resolution: Fixed

> 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
>          Components: Java-Chassis
>            Reporter: liubao
>            Assignee: liubao
>            Priority: Major
>             Fix For: java-chassis-1.0.0-m2
>
>
> 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)