On Fri, 4 May 2012, Jeff King wrote:
The absolute simplest way for us would be to stop using CURLOPT_PROXYUSERNAME/PASSWORD to set it ahead of time, and instead provide a callback that curl would call on a 407. That callback would just need the URL of the proxy, and would return the username/password (or even just set them on the curl object via CURLOPT_PROXYUSERNAME/PASSWORD).For that matter, it would simplify our code to do the same for regular http auth, too. And though we usually know our URL in that case, we might not if we got a 302 with FOLLOWLOCATION set.
Thanks a lot. That is in fact almost exactly the solution we're discussing right now.
-- / daniel.haxx.se -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
[Newbies FAQ] [Linux Kernel Development] [Free Online Dating] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Free Online Dating] [Photo] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users] [Linux Resources]