#44456 [Bgs]: CURLOPT_URL error in parsing ftp url string given

ID: 44456 User updated by: sergiocrz at hotmail dot com Reported By: sergiocrz at hotmail dot com Status: Bogus Bug Type: cURL related Operating System: WinXP PHP Version: 5.2.5 New Comment: Those letters are not valid in a URL, described in RFC2396. (lib)curl expects and requires a valid URL. I didnt read that document, but I know that some clients' ftp servers use this kind of chars in the username and password and they are valid for login in wathever program, execpt CURL and php. thats tricky Previous Comments: ------------------------------------------------------------------------ [2008-03-24 00:58:02] felipe@php.net Nice, thanks for information, Daniel. ------------------------------------------------------------------------ [2008-03-23 23:40:32] daniel at haxx dot se Those letters are not valid in a URL, described in RFC2396. (lib)curl expects and requires a valid URL. ------------------------------------------------------------------------ [2008-03-19 02:34:31] felipe@php.net > Why is it expected that curl returns false > ip when the url contains '#'? AFAIK, the problem isn't the '#', but the '@'. ------------------------------------------------------------------------ [2008-03-19 02:28:19] sergiocrz at hotmail dot com Why is it expected that curl returns false ip when the url contains '#'? If I use rawurlencode() to username and password CURL will consider that encoded string as a new username and password, it will not be decoded on exec. The returning error is: Access denied: 530. Thats because the user and pass are incorrect... By the results I have I still think there is a bug somewhere... ------------------------------------------------------------------------ [2008-03-19 00:09:18] felipe@php.net This seems expected. Normally app. accepts the format obtained for: http://docs.php.net/manual/en/function.rawurlencode.php Try using this function on login and password. ------------------------------------------------------------------------ The remainder of the comments for this report are too long. To view the rest of the comments, please view the bug report online at http://bugs.php.net/44456 -- Edit this bug report at http://bugs.php.net/?id=44456&edit=1