• 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: stringWithContentsOfURL with resulting error 256
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: stringWithContentsOfURL with resulting error 256


  • Subject: Re: stringWithContentsOfURL with resulting error 256
  • From: John Horigan <email@hidden>
  • Date: Thu, 22 Oct 2009 11:11:51 -0700

Try using curl (the command-line utility) to see _exactly_ what Cocoa gets from the server when it accesses that URL. The server could be doing something that confuses Cocoa but which PHP and Safari handle properly.

-- john

On Oct 22, 2009, at 8:52 AM, Jens Alfke wrote:


On Oct 22, 2009, at 7:16 AM, James Lin wrote:

NSString *result = [NSString stringWithContentsOfURL:theURL encoding:NSUTF8StringEncoding error:&error];
However, the result comes back with an NSError as the following:
Error Domain=NSCocoaErrorDomain Code=256 UserInfo=0x15d7b0 "Operation could not be completed. (Cocoa error 256.)
which is a NSFileReadUnknownError = 256.
BUT! The same URL string works perfectly in a Safari window and the PHP script executes fine when accessed from Safari...

That's a weird error I haven't seen before — looks like a generic "duh, something went wrong" fallback.


My first guess is that NSString can't decode the URL response into a string due to encoding issues; maybe the content uses an encoding that's incompatible with UTF-8? I would start trying lower-level calls to find the point where it starts to work.
-[NSString stringWithContentsOfURL:usedEncoding:error:]
-[NSData dataWithContentsOfURL:...]
-[NSURLConnection sendSynchronousRequest:...]


Note that in most cases you don't want to use this type of synchronous call on a remote URL because it blocks the thread for an arbitrary amount of time. The usual Cocoa style is to use an asynchronous request via NSURLRequest.

—Jens_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden

_______________________________________________

Cocoa-dev mailing list (email@hidden)

Please do not post admin requests or moderator comments to the list.
Contact the moderators at cocoa-dev-admins(at)lists.apple.com

Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


  • Follow-Ups:
    • Re: stringWithContentsOfURL with resulting error 256
      • From: James Lin <email@hidden>
References: 
 >stringWithContentsOfURL with resulting error 256 (From: James Lin <email@hidden>)
 >Re: stringWithContentsOfURL with resulting error 256 (From: Jens Alfke <email@hidden>)

  • Prev by Date: Re: NSTextField not getting mouseDown
  • Next by Date: Textured sheet with tabview
  • Previous by thread: Re: stringWithContentsOfURL with resulting error 256
  • Next by thread: Re: stringWithContentsOfURL with resulting error 256
  • Index(es):
    • Date
    • Thread