RE: [lwip-users] LWIP Timeout(?) 2 second to ACKnowledge the endof the transmission. log file TC_IP trace2.pcap

[Damon, Antoine]

Hi


I modified the response of the webserver. Now, there is no error in the log, 
but for
each transfer the web server gives the order to open/close a connection. The 
stack need
1.4 secondes to open the connection, I would like to know how to reduce this 
time? 
You could see in the log line 21/22,36/37,48:49....
Thanks for your help
Best regards
Antoine Damon 

-----Message d'origine-----
De : address@hidden
[mailto:address@hidden De la part de
address@hidden
Envoyé : mardi 5 octobre 2010 20:23
À : Mailing list for lwIP users
Objet : Re: [lwip-users] LWIP Timeout(?) 2 second to ACKnowledge the endof the
transmission. log file TC_IP trace2.pcap


  Kieran Mansley wrote:
> On Tue, 2010-10-05 at 09:48 -0400, Damon, Antoine wrote:
>> Have you got an idea about this timeout(?).
> Sounds like the server is just waiting before closing the socket,
> perhaps because it's giving the client a chance to send another request
> but doesn't want to leave sockets open indefinitely.
Well, that's a bit odd. An HTTP/1.1 server SHOULD use the 
"Content-Length" field to indicate the length of the body (RFC 2616, 
section 14.13). If this field is not given, the only means to tell the 
client that the body is finished is closing the connection (section 
4.4). This is especially used when the webserver does not know the 
content length when sending the header (see below).

Also, if "Content-Length" is missing, the connection cannot be reused 
since the client does not know when the server has finished the previous 
body.

Looks like a bug in the Go-Ahead webserver (well, it's not violating the 
RFC, it's a bit slow only). But it could well be produced by the 
application running the webserver as the data returned seems to be 
generated rather than compiled-in. In this case, the server might not 
know the body length in advance and gets informed too late that the end 
is rechached.

Maybe you might want to check your application code in that direction...

Simon

_______________________________________________
lwip-users mailing list
address@hidden
http://lists.nongnu.org/mailman/listinfo/lwip-users

* * * * * * * * * * * * *
This e-mail is intended solely for the intended recipient or recipients. If 
this e-mail is addressed to you in error or you otherwise receive this e-mail 
in error, please advise the sender, do not read, print, forward or save this 
e-mail, and promptly delete and destroy all copies of this e-mail. 
This email may contain information that is confidential, proprietary or secret 
and should be treated as confidential by all recipients. This e-mail may also 
be a confidential attorney-client communication, contain attorney work product, 
or otherwise be privileged and exempt from disclosure. If there is a 
confidentiality or non-disclosure agreement or protective order covering any 
information contained in this e-mail, such information shall be treated as 
confidential and subject to restriction on disclosure and use in accordance 
with such agreement or order, and this notice shall constitute identification, 
labeling or marking of such information as confidential, proprietary or secret 
in accordance with such agreement or order.
The term 'this e-mail' includes any and all attachments.
* * * * * * * * * * * * *

TCP_IP_WS_trace.pcap
Description: TCP_IP_WS_trace.pcap