-
-
Notifications
You must be signed in to change notification settings - Fork 6.7k
FTP: CURLFTPMETHOD_NOCWD does not URL-decode the path #1974
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I'm basically having the same issue as in #1812 |
Then you should have read @bagder 's comment on the issue: #1812 (comment) |
Okay, let's see what happens when we urlencode the string... lstArg becomes /dir/%23name, still file not found, ups... Remember, Curl does not urldecode the string in the CURLFTPMETHOD_NOCWD case |
That is a bug. |
I can't reproduce. So I edited test 298 to use an URL encoded path with nocwd (see commit above) and it works just fine. |
It seems CURLOPT_CUSTOMREQUEST "MLSD" is needed to reproduce |
Not quite. But it seems a directory listing is needed! |
Reported-by: Zenju on github Test 244 added to verify Fixes #1974
I did this
An FTP transfer with
CURLFTPMETHOD_NOCWD
selected.A URL with one or more URL encoded "letters".
I expected the following
The path to be URL decoded by curl before use.
curl/libcurl version
any
operating system
any
The text was updated successfully, but these errors were encountered: