At 15:33 3/12/2007, you wrote:
> Anyway - I answered my own question.
> I wrote a test, Keep Alive works fine with chunked content.
So... what was the problem? For days you've been railing against Tomcat
for not supporting this properly. Is there something that you overlooked?
- -chris
Part
I answered my own question here:
The client must send the *complete* sequence
"\r\n0\r\n\r\n" or tomcat *will* hang attempting to read the last
"\r\n" after the last "zero length chunk" No one including myself caught this.
PK
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Kennard wrote:
> Anyway - I answered my own question.
> I wrote a test, Keep Alive works fine with chunked content.
So... what was the problem? For days you've been railing against Tomcat
for not supporting this properly. Is there someth
Anyway - I answered my own question.
I wrote a test, Keep Alive works fine with chunked content.
If anyone wants the test code let me know. (should I post it?) It
is small - about 150 lines worth, all java.
PK
Does Tomcat support Keep Alive, as a stand alone server, for
multiple Client POS
Does Tomcat support Keep Alive, as a stand alone server, for multiple
Client POST requests to different servlet paths where both request
and response are "Transfer-Encoding: chunked"?
Is there a definition somewhere of when tomcat will drop a connection
when keep-alive is specified?
Thanks.
What if you use a non-chunked request? You asked already and the
response was that TC basically doesn't handle chunked requests.
TC handles chunked requests in all ways except that it doesn't have a
methodology in the servlet API (EOFException etc) for notifying you
if you try to read beyond
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Kennard wrote:
> The "0" is the hex digint "Zero" the "terminal EOD" chunk is defined in
> HTTP1.1 as a chunk with a length of 0. This is what terminates the data
> for the current request.
EOF? Right, I forgot that you were using chunk
At 19:50 3/10/2007, you wrote:
The "0" is the hex digint "Zero" the "terminal EOD" chunk is defined
in HTTP1.1 as a chunk with a length of 0. This is what terminates
the data for the current request.
I tried "explicitly" putting in the keep alive header, though it is
deprecated in HTTP1.1 a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Peter,
Peter Kennard wrote:
> for HTTP1.1 (in tomcat 6)
>
> Does tomcat handle keep alive (ie: keeping a connection open for
> subsequent requests)
>
> If so under what circumstances is the connection closed (or kept open)?
>
> Sending chunked cont
for HTTP1.1 (in tomcat 6)
Does tomcat handle keep alive (ie: keeping a connection open for
subsequent requests)
If so under what circumstances is the connection closed (or kept open)?
Sending chunked content, with a terminal "\r\n0\r\n" will cause the
connection to be disconnected.
As does
10 matches
Mail list logo
