home bbs files messages ]

Forums before death by AOL, social media and spammers... "We can't have nice things"

   comp.protocols.tcp-ip      TCP and IP network protocols.      14,669 messages   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]

   Message 13,168 of 14,669   
   glen herrmannsfeldt to mockturtle   
   Re: Funny problem with TCP: 1 char per p   
   11 Nov 09 22:00:28   
   
   028d3b6e   
   From: gah@ugcs.caltech.edu   
      
   mockturtle  wrote:   
      
   > I have a program that communicates with an HTTP server (lighttpd) [it   
   > is not an HTTP issue, stay with me...].  Both server and client run on   
   > the same PC and talk via 127.0.0.1. On my home computer everything   
   > goes fine, but when I run them (the server and the client) on my   
   > office computer the  server closes the connection as soon as it sees   
   > the double CRLF at the end of the query.  By looking at the traffic   
   > with wireshark and/or tcpdump I can see that on my office computer my   
   > client is sending the 1 char per packet, that is the request (say)   
   > "GET /index.html ..." is being sent   
      
   > "G"   
   > "E"   
   > "T"   
   > " "   
   > "/"   
      
   > ... and so on...  I guess that the server should not care (my client   
   > can distribute the data in the packets as it wishes), but I suspect   
   > that this extreme fragmentation can "confuse" it.   
      
   TCP is a stream protocol.   
      
   If that confuses it, then it is a bug in the receiver.   
      
   -- glen   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)   

[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]


(c) 1994,  bbs@darkrealms.ca