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

Posted to dev@thrift.apache.org by "Rowan Kerr (JIRA)" <ji...@apache.org> on 2011/02/09 19:31:57 UTC

[jira] Updated: (THRIFT-1030) C++ THttpTransport doesn't support chucked transfer encoding

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

Rowan Kerr updated THRIFT-1030:
-------------------------------

    Attachment: THRIFT-1030-iequals.patch

This is caused by response headers with "transfer-encoding" instead of the expected "Transfer-Encoding" string.

Attaching patch to do case-insenstive comparison of headers.

> C++ THttpTransport doesn't support chucked transfer encoding
> ------------------------------------------------------------
>
>                 Key: THRIFT-1030
>                 URL: https://issues.apache.org/jira/browse/THRIFT-1030
>             Project: Thrift
>          Issue Type: Improvement
>          Components: C++ - Library
>    Affects Versions: 0.5
>            Reporter: changning zhou
>         Attachments: THRIFT-1030-iequals.patch
>
>
> With the chucked transfer encoding, the response of HTTP doesn't have "content-length", instead it has "transfer-encoding:chunked", and send the content by chucks. But the c++ thrift library will treat it as no data, and throw TTransportException.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira