Re: CFHTTPMessageAddAuthentication problem
Re: CFHTTPMessageAddAuthentication problem
- Subject: Re: CFHTTPMessageAddAuthentication problem
- From: Frederick Cheung <email@hidden>
- Date: Mon, 02 Dec 2013 14:15:34 +0000
>
> How did you create the response? Some HTTP authentication methods require that the original URL be available in the response. This happens automatically for responses you get from CFHTTPStream (via kCFStreamPropertyHTTPResponseHeader) but does not happen automatically for responses you create yourself. The real kicker is that there's no public API to set this response URL; there's a fairly well-known private API, _CFHTTPMessageSetResponseURL, but that's not the same thing )-:
>
> We're tracking this limitation as <rdar://problem/6980095>.
>
> Please try using _CFHTTPMessageSetResponseURL and see if that gets authentication working. If it does, let me know and I'll update the bug to indicate your interest in a fix. And in that case the only /supported/ workaround is to implement Digest authentication yourself.
This was all a long time ago, but I filed a radar back in 2007 about the lack of public alternative to _CFHTTPMessageSetResponseURL (5006224) and was eventually told it was behaving as intended.
Fred
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macnetworkprog mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden