On Tue, 22 Mar 2005, Dan Fandrich wrote:

> How about three new options:
> CURLOPT_USERNAME
> CURLOPT_PASSWORD
> CURLOPT_ENABLE_AUTH
>
> New code would have to set CURLOPT_ENABLE_AUTH to have any authentication.
> Then CURLOPT_USERPWD would be deprecated and rewritten internally to do
> CURLOPT_ENABLE_AUTH, CURLOPT_USERNAME and CURLOPT_PASSWORD.
> CURLOPT_ENABLE_AUTH could even be a renamed and generalized CURLOPT_HTTPAUTH.
>
> This would be backwards-compatible yet give a cleaner interface going
> forward for new apps. Am I missing anything?

I think I like it. But we would need three more options though to cover the
same stuff for proxies too...

I'll go away for a mini-vacation now for a few days, and I'll try to give this
some more thought during it.

-- 
      Daniel Stenberg -- http://curl.haxx.se -- http://daniel.haxx.se
  Commercial curl and libcurl Technical Support: http://haxx.se/curl.html