For what it's worth, I am in the situation where my HTTP and FTP
proxies use two different passwords. But I don't know how common
it is either...

I can see your point about storing both options in your .curlrc
file simultaneously... Currently curl can run multiple URLs
(each with their own -o option) just by specifying more than
one set of these. Perhaps curl could support entering two
different sets of proxy info in the same file, and could track
BOTH an FTP option and an HTTP option internally, while still
using the same command-line flags? This way, those of us who
only occasionally use these options could still have the single
character format available, while those who use .curlrc files could
still store both.

I'm thinking of something like this:

-x proxy.domain.com:80
    (OR -x http://proxy.domain.com, with http being the default)
-U user:pass
-x ftp://proxy.domain.com:port/proxy-type
    (OR add --ftp-proxy-type XYZ instead)
-U ftpuser:ftppass

- Kevin

-----Original Message-----
From: Philip Newton [mailto:pnewton_at_gmx.de]
Sent: Monday, April 14, 2003 10:59 AM

On the other hand, using new options means that users will be able to
pre-set proxy-user differently for HTTP and FTP in their ~/.curlrc.
(Though I don't know how often they will be different; I imagine that
if a site has an HTTP and an FTP proxy and they both require
authentication, they will accept the same credentials. Requiring them
to be the same, or requiring explicit overriding on the commandline,
may be sufficient.)

-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
Received on 2003-04-14