In general CFNetwork internal errors are just that, internal errors. The standard response is to file a bug describing the error. It'd be best if you included a small test project that illustrates the problem, hopefully pointing at a test server that reproduces the problem. If the relevant server isn't public, you should include a packet trace and a CFNetwork diagnostics log.If you do file a bug, please post your bug number here, just for the record.Is the error accompanied by an actual failure? That is, does the request work and you just get this error message? If so, it's reasonable to just ignore it.Finally, the error seems to be associated with how CFNetwork handles multipart/x-mixed-replace content. In general CFNetwork handles that reasonable well. Are you sure that your server is generated correctly formed multipart/x-mixed-replace content?Share and Enjoy — Quinn The Eskimo! Apple Developer Relations, Developer Technical Support, Core OS/Hardware let myEmail = eskimo + 1@apple.com
Topic:
App & System Services
SubTopic:
Networking
Tags: