Hi Kay.
It might not be as bad as you think to handle cookies yourself. The
methods +[NSHTTPCookie cookiesWithResponseHeaderFields:forURL:] and +
[NSHTTPCookie requestHeaderFieldsWithCookies:] are useful. You should
also be able to archive -[NSHTTPCookie properties]. Thus, it's not an
enormous amount of effort to maintain your own cookie list.
I think everyone agrees that the lack of per-app NSHTTPCookieStorage
is terrible, though. (Turns out the shared URL cache isn't thread-safe
either.)
-Jeff
On Apr 28, 2009, at 1:57 AM, Kay Jurkuhn wrote:
Hi list!
I've tried to establish some http communication with the help of the
URL loading system.
I had to discover that the cookie accept policy setting of the
shared cookie storage effects all applications
using the URL loading system. My application needs to accept cookies
at all times.
So what I don't want to do is to change the accept policy setting
temporarily. This would mean a security risk for all other apps.
Another way would be not to use the automatic cookie handling and to
handle the cookies myself which is undesirable
because of all the effort it would take to implement.
Is there another way to change the cookie accept setting only for my
application/process to accept all cookies?
Best Regards
Kay
_______________________________________________
Cocoa-dev mailing list (Cocoa-dev@lists.apple.com)
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:
http://lists.apple.com/mailman/options/cocoa-dev/archive%40mail-archive.com
This email sent to arch...@mail-archive.com
