• 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: Known issues with CFHTTPStream?
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Known issues with CFHTTPStream?


  • Subject: Re: Known issues with CFHTTPStream?
  • From: Becky Willrich <email@hidden>
  • Date: Wed, 9 Oct 2002 11:52:45 -0700

Are there major known issues with CFHTTPStream? I'm encountering situations
where it returns a -1 (parse failure) error in the HTTP error domain.

I don't know of any known issues here; in particular, the only cases I've seen where a parse failure is returned have been legitimate server errors (the server returned data that was not a valid HTTP response, and could not be parsed as such).

I've seen two situations (one that seems to point to issues with HTTP 1.1
and chunked transfer-encoding, and the other seems to be somewhat less
concrete: timing related issues that may point to how it deals with
buffering of incoming data).

I've seen examples where the server omits the final CRLF from the final chunk, and causes a parse error to be returned up the stream; this is a valid parse failure (the HTTP transaction is not complete until that final CRLF comes in), but is of little use since the client can't tell whether the error occurred on the final chunk or an earlier one. If this is what you're running in to, the workaround is to assume the data you've received is valid and see if it contains all the content you're expecting.

Before I spend a lot of time developing workarounds or generating test cases
for bug reports (and maybe ultimately writing a new HTTP backend for our
code...) are there known issues with this code?

I've posted the exhaustive list of known issues (to the best of my knowledge) on this list before; if you search the archives, you should find it pretty quickly. That might be a good place to start. However, from your description, I suspect either a faulty HTTP server or a faulty proxy en route to the server. I vote for the test cases for bug reports. :)

REW
_______________________________________________
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.

References: 
 >Known issues with CFHTTPStream? (From: James Berry <email@hidden>)

  • Prev by Date: CFNetService - PB vs. CodeWarrior problems
  • Next by Date: Re: Re(4): Is PPP connected
  • Previous by thread: Known issues with CFHTTPStream?
  • Next by thread: Re: Re(4): Is PPP connected
  • Index(es):
    • Date
    • Thread