Re: NSURLConnection willSendRequest: not behaving as expected on a 302 response - no further response after nil return

2009-05-14 Thread Cédric Luthi
This was indeed a bug and has been fixed in Mac OS X 10.5.7 See http://www.openradar.me/6700222 for the bug report. ___ Cocoa-dev mailing list (Cocoa-dev@lists.apple.com) Please do not post admin requests or moderator comments to the list. Contact the

Re: NSURLConnection willSendRequest: not behaving as expected on a 302 response - no further response after nil return

2008-10-06 Thread Jerry Krinock
Fortunately for me I probably never read the documentation you quoted :) What I've done for a similar purpose, is to wait until I've got all the data I want in hand, and then send it a -cancel. Works fine. ___ Cocoa-dev mailing list (Cocoa-dev@

NSURLConnection willSendRequest: not behaving as expected on a 302 response - no further response after nil return

2008-10-04 Thread Steve Mykytyn
I'm using NSURLConnection to contact a URL that returns a 302 response along with some data, and then returns a 200 response with some different data. I want to stop it at the 302 response and get the data that comes along with the 302 response. To make this happen I understand the delegate meth