From: barmar@alum.mit.edu   
      
   In article ,   
    Torsten Robitzki  wrote:   
      
   > Hello,   
   > from what I've read in RFC 2616 (http 1.1), there is neither a   
   > keep-alive header nor a keep-alive connection-header option specified.   
   >  From three browsers I've tested, all of them send a   
   >   
   >    "Connection: keep-alive"   
   >   
   > header and one of them send a   
   >   
   >    "Keep-alive: 115"   
   >   
   > header. All claim to use HTTP version 1.1.   
   >   
   > What might be the reason, why they send such headers? And what might be   
   > the expected behaviour (especially in conjunction with the keep-alive   
   > header) of a server? Are there any RFCs describing keep-alive with HTTP 1.1?   
   >   
   > best regards   
   > Torsten   
      
   Before RFC 2616 was written, server authors experimented with different   
   ways to specify keep-alive.  Some used the "Keep-alive:" header, others   
   used "Connection: keep-alive".  So browsers started sending these   
   headers.   
      
   Now they continue doing so for compatibility.   
      
   --   
   Barry Margolin, barmar@alum.mit.edu   
   Arlington, MA   
   *** PLEASE don't copy me on replies, I'll read them in the group ***   
      
   --- SoupGate-Win32 v1.05   
    * Origin: you cannot sedate... all the things you hate (1:229/2)