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,968 of 14,669    |
|    Jorgen Grahn to Mark    |
|    Re: tcp segments with HTTP traffic    |
|    04 Apr 13 14:54:24    |
      From: grahn+nntp@snipabacken.se              On Thu, 2013-04-04, Mark wrote:       > Hello,       >       > I'm implementing a http parser; As indicator of http data I'm searching for       > 'HTTP/1.? CRLF' in the stream.       > TCP layer may cut the application-provided buffer into chunks suitable for       > transferring over network. Is it possible to have http data (e.g. GET       > http://www.google.com/index.html HTTP/1.1 CRLF) NOT following immediately       > after TCP header?              I don't understand. If you're running HTTP, that means all TCP       payload is HTTP data, and the TCP payload by definition follows       immediately after the TCP header (including TCP options, if any).              > Also, is it possible to have, for example 'GET ..' query       > split across TCP segments?              Yes. Why do you ask? You wrote that you're looking at the TCP stream;       there are no segments on that level. (And no TCP header, for that       matter,)              /Jorgen              --        // Jorgen Grahn |
[   << oldest   |   < older   |   list   |   newer >   |   newest >>   ]
(c) 1994, bbs@darkrealms.ca