NSHTTPURLHandle bugs
NSHTTPURLHandle bugs
- Subject: NSHTTPURLHandle bugs
- From: Finlay Dobbie <email@hidden>
- Date: Sun, 27 Jan 2002 20:07:27 +0000
I'm currently using NSHTTPURLHandle to download data. Currently I'm
using
http://localhost/somefile as a placeholder and for testing. I
found that if my application crashes with SIGPIPE if Apache isn't
running.
Backtrace:
#0 0x70002938 in write ()
#1 0x701dd8e0 in fdWrite ()
#2 0x701e4cdc in socketWrite ()
#3 0x701c0ed8 in CFWriteStreamWrite ()
#4 0x75181e1c in CFHTTPMessageCopyBody ()
#5 0x75181c58 in CFHTTPMessageCopyBody ()
#6 0x75182e78 in CFHTTPMessageIsHeaderComplete ()
#7 0x701c9bb8 in _CFStreamGetCallBackPtr ()
#8 0x70829d08 in -[NSHTTPURLHandle beginLoadInBackground] ()
#9 0x708afb38 in -[NSURLHandle loadInBackground] ()
... etc ...
Uhm... Shouldn't it be calling the NSURLHandleClient -
(void)URLHandle:(NSURLHandle *)sender
resourceDidFailLoadingWithReason:(NSString *)reason method instead? This
isn't really likely to be a problem in the production environment, but
then of course because it's not likely means that it will definitely
happen :-)
Any workarounds other than installing a signal handler (and where to
look for docs on that... a manpage, perhaps)? :-)
-- Finlay