You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2015/07/24 16:52:05 UTC
[jira] [Resolved] (CAMEL-9013) Camel HTTP no longer supporting
chunked transfer encoding with Tomcat
[ https://issues.apache.org/jira/browse/CAMEL-9013?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Claus Ibsen resolved CAMEL-9013.
--------------------------------
Resolution: Fixed
Assignee: Claus Ibsen
Fix Version/s: 2.15.3
> Camel HTTP no longer supporting chunked transfer encoding with Tomcat
> ---------------------------------------------------------------------
>
> Key: CAMEL-9013
> URL: https://issues.apache.org/jira/browse/CAMEL-9013
> Project: Camel
> Issue Type: Bug
> Components: camel-http, camel-servlet
> Affects Versions: 2.15.0, 2.15.1, 2.15.2
> Reporter: Bob Browning
> Assignee: Claus Ibsen
> Fix For: 2.15.3
>
>
> When sending a chunked POST whilst running the servlet under Tomcat, camel now fails to read the input stream and sets the body to null.
> [chunked-http-failure-test|https://github.com/ukcrpb6/chunked-http-failure-test]
> This is due to camel checking the stream for available bytes introduced in CAMEL-5806. For whatever reason the CoyoteInputStream is returning 0 available bytes when handling a chunked request.
> {code}
> if (len < 0) {
> InputStream is = request.getInputStream();
> if (is.available() == 0) {
> // no data so return null
> return null;
> }
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)