• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: Reading HTTP headers (was Re: cfsockets vs OT)
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Reading HTTP headers (was Re: cfsockets vs OT)


  • Subject: Re: Reading HTTP headers (was Re: cfsockets vs OT)
  • From: Joseph Kim <email@hidden>
  • Date: Tue, 6 Jan 2004 01:24:39 -0600

On Jan 6, 2004, at 12:31 AM, Larry Gerndt wrote:

This raises a question I've long had: in HTTP, what is the best way to read
in the HTTP header? The only way that makes sense to me is to read one byte
at a time until I see the header terminator, 0x0D0A0D0A, because there is no
way of knowing how big the header is. Am I missing something?

General technique is to read() big chunks and do your
protocol parsing from the buffer. You generally don't
want to make N system calls to read/write N bytes.
_______________________________________________
macnetworkprog mailing list | email@hidden
Help/Unsubscribe/Archives: http://www.lists.apple.com/mailman/listinfo/macnetworkprog
Do not post admin requests to the list. They will be ignored.

  • Follow-Ups:
    • Re: Reading HTTP headers (was Re: cfsockets vs OT)
      • From: Becky Willrich <email@hidden>
References: 
 >Reading HTTP headers (was Re: cfsockets vs OT) (From: Larry Gerndt <email@hidden>)

  • Prev by Date: Reading HTTP headers (was Re: cfsockets vs OT)
  • Next by Date: Re: Bringing Up TCP/IP?
  • Previous by thread: Reading HTTP headers (was Re: cfsockets vs OT)
  • Next by thread: Re: Reading HTTP headers (was Re: cfsockets vs OT)
  • Index(es):
    • Date
    • Thread