[
https://issues.apache.org/jira/browse/ASTERIXDB-1939?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16045846#comment-16045846
]
ASF subversion and git services commented on ASTERIXDB-1939:
------------------------------------------------------------
Commit f0759c85b70d18fe9376cdc034ed9e70e1ec0c74 in asterixdb's branch
refs/heads/master from [~tillw]
[ https://git-wip-us.apache.org/repos/asf?p=asterixdb.git;h=f0759c8 ]
ASTERIXDB-1939: No chunked encoding with content-length.
Change-Id: I06d561eb023f1c84c531e9b2cfe88a626d7e5280
Reviewed-on: https://asterix-gerrit.ics.uci.edu/1632
Sonar-Qube: Jenkins <[email protected]>
Tested-by: Jenkins <[email protected]>
BAD: Jenkins <[email protected]>
Reviewed-by: Michael Blow <[email protected]>
Integration-Tests: Jenkins <[email protected]>
> Query Service API returns content-length for chunked transfer encoding
> ----------------------------------------------------------------------
>
> Key: ASTERIXDB-1939
> URL: https://issues.apache.org/jira/browse/ASTERIXDB-1939
> Project: Apache AsterixDB
> Issue Type: Bug
> Components: HTTP API
> Reporter: Till
> Assignee: Till
>
> In some cases the Hyracks HTTP server returns responses that specify that the
> {{chunked}} transfer encoding is used and they also provide a
> {{Content-Length}} header. We have seen at least 2 clients that do not handle
> this combination.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
