On Tue, 7 Feb 2012, Chandrakant Bagul -ERS, HCL Tech wrote:

>> I believe this is because if libcurl fails to parse/accept the proxy string
>> it won't get set and then it runs without proxy. I think that is the
>> correct behavior, but you should of course get an error code back when you
>> used setopt() to set that proxy. Did you?
>
> We didn't get any error when setopt() is used to set the invalid proxy, it
> always returns CURLE_OK.

Yes, right. I was being stupid - setopt() basically only copies the string and
does no parsing whatsoever. I could repeat your problem and I've now pushed a
fix for this with an associated test case (1329). Thanks for reporting!

-- 
  / daniel.haxx.se
-------------------------------------------------------------------
List admin: http://cool.haxx.se/list/listinfo/curl-library
Etiquette:  http://curl.haxx.se/mail/etiquette.html