/apr data lost in http post request?
Can MSIE even control which data goes in which packet?
TCP/IP APIs on most platforms allow the Nagle algorithm to be disabled, which
will cause data to be sent out on each call. Most TCP/IP stacks also set the
push flag on the last packet
Hi Chris,
Raising the keepalive-timeout value on the connector definitely improves
the situation.
From what I've gathered from what people posted here (thanks guys) and
dumping packets I believe the situation to be somewhat as follows:
With nagle's off, IE sends out the http request in two
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
No, you'd need to modify the source. It's not particularly useful in
most scenarios to intentionally stall an HTTP conversation, so it's not
a built-in feature :)
No, I'm saying that you should send
Taylan Develioglu wrote:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
No, you'd need to modify the source. It's not particularly useful in
most scenarios to intentionally stall an HTTP conversation, so it's not
a built-in feature :)
No, I'm saying that
Hi Andre,
I meant to stop writing, not closing the socket. Poor choice of words,
apologies.
André Warnier wrote:
Taylan Develioglu wrote:
Christopher Schultz wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
No, you'd need to modify the source. It's not particularly useful
Christopher Schultz wrote:
Can MSIE even control which data goes in which packet? That would seem
to be part of the TCP/IP stack, buried in the OS, and affecting both
MSIE and any other browser on the same system.
We saw that Firefox uses only one packet to send a POST request (of
distribution to any party other than intended recipient. Sender does
not necessarily endorse content contained within this transmission.
To: users@tomcat.apache.org
From: oliver.scho...@capgemini-sdm.com
Subject: Re: tomcat w/apr data lost in http post request?
Date: Thu, 12 Mar 2009 16:55:04
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oliver,
On 3/10/2009 2:41 PM, Oliver Schoett wrote:
As far as I know, splitting header and body of POST requests into
separate TCP packets is a peculiarity of IE browsers. This observation
was made using normal HTML forms, but it may well apply
From: Christopher Schultz [mailto:ch...@christopherschultz.net]
Subject: Re: tomcat w/apr data lost in http post request?
Can MSIE even control which data goes in which packet?
TCP/IP APIs on most platforms allow the Nagle algorithm to be disabled, which
will cause data to be sent out
Taylan Develioglu wrote:
I would like to correct this, it seems to only happen with IE6/7.. maybe
old firefox 2.0
We recently observed a similar problem. When IE 6/7/8 make a form POST,
they often send the header in one TCP packet and the body in another. A
flaky networking component
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
On 3/5/2009 5:45 AM, Taylan Develioglu wrote:
Can the wget clone do this without modification, or do I need to change it?
No, you'd need to modify the source. It's not particularly useful in
most scenarios to intentionally stall an HTTP
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Taylan,
On 3/6/2009 4:05 AM, Taylan Develioglu wrote:
James, thank you very much.
I suspected IE to be guilty because it was happening only with IE clients.
Chris, I guess we don't need to try and reproduce this anymore now we
know the
I would like to correct this, it seems to only happen with IE6/7.. maybe
old firefox 2.0
It happens with different clients indeed.
-
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands,
13 matches
Mail list logo
