From 08cf6780ba8ea242cb451f07e14bb572079e22cf Mon Sep 17 00:00:00 2001 From: Daniel Stenberg Date: Wed, 8 Oct 2008 10:39:43 +0000 Subject: - Igor Novoseltsev brought a patch that introduced two new options to curl_easy_setopt: CURLOPT_USERNAME and CURLOPT_PASSWORD that sort of deprecates the good old CURLOPT_USERPWD since they allow applications to set the user name and password independently and perhaps more importantly allow both to contain colon(s) which CURLOPT_USERPWD doesn't fully support. --- docs/KNOWN_BUGS | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) (limited to 'docs/KNOWN_BUGS') diff --git a/docs/KNOWN_BUGS b/docs/KNOWN_BUGS index 2c263e72c..dcc693cb9 100644 --- a/docs/KNOWN_BUGS +++ b/docs/KNOWN_BUGS @@ -160,10 +160,10 @@ may have been fixed since this was written! doesn't do a HEAD first to get the initial size. This needs to be done manually for HTTP PUT resume to work, and then '-C [index]'. -7. CURLOPT_USERPWD and CURLOPT_PROXYUSERPWD have no way of providing user names - that contain a colon. This can't be fixed easily in a backwards compatible - way without adding new options (and then, they should most probably allow - setting user name and password separately). +7. CURLOPT_PROXYUSERPWD has no way of providing user names that contain a + colon. This can't be fixed easily in a backwards compatible way without + adding new options. CURLOPT_USERPWD was split into CURLOPT_USERNAME and + CURLOPT_PASSWORD for this reason. 6. libcurl ignores empty path parts in FTP URLs, whereas RFC1738 states that such parts should be sent to the server as 'CWD ' (without an argument). -- cgit v1.2.3