:-)
I have example captures of some x509 related protocols running atop http which show this.
I will try to look into implementing this in the tcp layer this weekend.
On 9/8/06, Bryant Eastham <beastham@xxxxxxxxxxx> wrote:
What nagle algorithm! Did I forget to mention that we *wrote* the TCP/IP
stack and that it is running on a small microprocessor? ;-)
Seriously, this behavior is coming out of Tomcat Web Server/3.3.1 Final
(JSP
1.1; Servlet 2.2). We do, however, have our own implementations in
which nagle is not available. I would have to check with the developer
to see if he has disabled anything - I doubt it.
Thanks,
Bryant
________________________________
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx
] On Behalf Of ronnie
sahlberg
Sent: Thursday, September 07, 2006 5:32 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Further HTTP woes...
"I now have the following problem. It is common for our implementation
to
dump the headers in one segment and then dump the data in the next, with
no Content-Length."
Why does it send this as two segments?
You have not disabled NAGLE have you?
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev