Re: [lwip-users] http server problems/bug

[lampo]

> On LwIP side when you close a connection using the tcp_close it closes
> ALL.

Does that mean it closes all other connections including other independent
threads,like tcp client ,tcp server in our multithreaded system? 


> From having problems in some TCP module that I wrote I found that if I
> call tcp_shutdown and only
> define shutdown the TX side the connection is closed only after getting
> the ACK.

sorry,I can't quite get it. In our example, you mean TX side is our web
server, RX side is browser from PC, right?    But browser has already 
got the ack from web server after it sends out FIN,and close the
connection,while in fact the TX side does not closed totally. 

can you show the process in following format ,so I can get it precisely?

 web server                       <------ GET  HTTP/1.1-----   web Client 
 web server (FIN_WAIT_1)  -------- FIN,PSH----------->   web Client 
 web server (FIN_WAIT_2)  <-------- ACK-------------      web Client 
 (web server will stay in FIN_WAIT_2 for we find it receives no ACK here )
 web server                     <-------- FIN--------------      web Client 
 web server                      -------- ACK------------->      web Client 
(web client receives the ack, so it  close the RX side connection, thus it
cannot respond to a  FIN now)




--
View this message in context: 
http://lwip.100.n7.nabble.com/http-server-problems-bug-tp27017p27032.html
Sent from the lwip-users mailing list archive at Nabble.com.