[Carbon-jira] [jira] Work started: (ESBJAVA-763) Need a way to preserve content-length header when binary relay is enabled

[Supun Kamburugamuva (JIRA)]

     [ https://wso2.org/jira/browse/ESBJAVA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Work on ESBJAVA-763 started by Supun Kamburugamuva.

> Need a way to preserve content-length header when binary relay is enabled
> -------------------------------------------------------------------------
>
>                 Key: ESBJAVA-763
>                 URL: https://wso2.org/jira/browse/ESBJAVA-763
>             Project: WSO2 ESB
>          Issue Type: Improvement
>    Affects Versions: 3.0.1
>            Reporter: Paul Hodchenkov
>            Assignee: Supun Kamburugamuva
>
> Content-Length header of request is not preserved when binary relay is configured (esb uses transfer-encoding:chunked in endpoints by default). This causes some backend services like apache fileupload to work incorrectly because it relies on content-length header to determine the size of uploaded file. Disabling chunked encoding inside a proxy will force ESB to load all content in memory in order to calculate the content-length header, however such action will fail with OutOfMemoryError for a huge content. Need a way to tell ESB to pass Content-Length header as is.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira