I agree with Brian that "anonymous_at_example.com" would be
a good FTP password, as long as it isn't blacklisted by
too many servers.

As far as changing the user-agent behavior, I'm not sure
how well-received it will be if the library suddenly starts
revealing information about itself that it didn't reveal
previously. Also, since one of your concerns was for curl
getting blamed for malicious activity, there might be some
nasty applications out there that are currently using libcurl,
and if they suddenly start advertising it, that might not be
such a good thing either.

Having said that, it might be nice to pre-define some
commonly used strings somewhere in the libcurl headers,
e.g.

#define CURL_UA_DEFAULT NULL /* Behave same as curl CLI client */

#define CURL_UA_EMPTY " " /* Send an empty User-Agent header */

#define CURL_UA_NONE "" /* Omit the User-Agent entirely */

/* Internet Explorer 6 on Windows XP */
#define CURL_UA_IE6 \
  "Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1)"

/* Firefox 2.0 on Windows XP */
#define CURL_UA_FFWIN \
  "Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) \
Gecko/20061204 Firefox/2.0.0.1"

/* Firefox 1.0 on Mac PPC */
#define CURL_UA_FFMAC \
  "Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; \
rv:1.7.12) Gecko/20050915 Firefox/1.0.7"

/* Safari 4 PPC */
#define CURL_UA_SAFARI \
"Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/521.25 \
(KHTML, like Gecko) Safari/521.24"

/* Some antique browser */
#define CURL_UA_NS1 "Mozilla/1.0 (Windows; I; 16bit)"
Received on 2007-02-13