Mailing-List: contact users-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Users List" <users@tomcat.apache.org>
Received-SPF: pass (nike.apache.org: local policy)
To: users@tomcat.apache.org
MIME-Version: 1.0
Subject: Tomcat and "Chunked Transfer-Encoding"
From: Walter.Heestermans@toyota-europe.com
Message-ID: 
 <OF7D810A09.3A7E34D4-ONC1257C74.0033B153-C1257C74.00349567@toyota-europe.com>
Date: Mon, 3 Feb 2014 10:34:21 +0100
Content-Type: multipart/mixed; boundary="=_mixed 00348C7FC1257C74_="

--=_mixed 00348C7FC1257C74_=
Content-Type: multipart/alternative;
 boundary="=_alternative 00348C7FC1257C74_="


--=_alternative 00348C7FC1257C74_=
Content-Type: text/plain; charset="US-ASCII"

Hi,

We have some weird behaviopur with one of our applications using 
apache-tomcat-6.0.37.

This is the report of the newtork engineer:

The application (or app server - apache/coyote) is returning a response 
with "Chunked Transfer-Encoding", but is sending the first chunks before 
giving the http headers (that defines the chunk-encoding).

The result is that the client receives a response stating by the 
definition on the chunk lenght (7a5), and as the header "Content-Encoding" 
has not been received, that length definition is interpreted as response 
characters.

Here is a dump of the communication between TARS Reverse Proxy and the 
Back-end. (You may notice the response headers - 200 OK - after the first 
chunk (in blue, starting by "7a5", the length in HEX )


See attached screenshot tcpstream.jpg.


Regards
Walter


This e-mail may contain confidential information.
If you are not an addressee or otherwise authorised to receive this message, you should not use, copy, disclose or take any action based on this e-mail. 
If you have received this e-mail in error, please inform the sender promptly and delete this message and any attachments immediately.
--=_alternative 00348C7FC1257C74_=
Content-Type: text/html; charset="US-ASCII"

<font size=2 face="sans-serif">Hi,</font>
<br>
<br><font size=2 face="sans-serif">We have some weird behaviopur with one
of our applications using apache-tomcat-6.0.37.</font>
<br>
<br><font size=2 face="sans-serif">This is the report of the newtork engineer:</font>
<br>
<table>
<tr>
<td><font size=2 face="Tahoma"><i>The application (or app server - apache/coyote)
is returning a response with &quot;Chunked Transfer-Encoding&quot;, but
is sending the first chunks before giving the http headers (that defines
the chunk-encoding).<br>
<br>
The result is that the client receives a response stating by the definition
on the chunk lenght (7a5), and as the header &quot;Content-Encoding&quot;
has not been received, that length definition is interpreted as response
characters.<br>
<br>
Here is a dump of the communication between TARS Reverse Proxy and the
Back-end. (You may notice the response headers - 200 OK - after the first
chunk (in blue, starting by &quot;7a5&quot;, the length in HEX )</i><br>
</font></table>
<br>
<table>
<tr>
<td><font size=2 face="Tahoma">See attached screenshot tcpstream.jpg.</font></table>
<br>
<br>
<br>
<br><font size=2 face="sans-serif">Regards</font>
<br><font size=2 face="sans-serif">Walter</font>
<br>
<br>
<br>
<br>
<span style="font-family:sans-serif,helvetica; font-size:10pt; color:#000000">This e-mail may contain confidential information.<br>
If you are not an addressee or otherwise authorised to receive this message, you should not use, copy, disclose or take any action based on this e-mail. <br>
If you have received this e-mail in error, please inform the sender promptly and delete this message and any attachments immediately.</span>
--=_alternative 00348C7FC1257C74_=--

--=_mixed 00348C7FC1257C74_=
Content-Type: text/plain; charset=us-ascii


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tomcat.apache.org
For additional commands, e-mail: users-help@tomcat.apache.org
--=_mixed 00348C7FC1257C74_=--