FTP: CURLFTPMETHOD_NOCWD does not URL-decode the path

[Zenju]

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

[Zenju]

I'm basically having the same issue as in #1812
When CURLFTPMETHOD_NOCWD is used and the URL contains a hash, e.g. "/dir/#name", then the rest including the hash is stripped, resulting in a file not found error because lstArg is "/dir/" from the code example in the other ticket.

[jzakrzewski]

Then you should have read @bagder 's comment on the issue: #1812 (comment)
Since "#" has special meaning in the URL, it must be URL-encoded when used outside it's meaning.

[Zenju]

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

[bagder]

That is a bug.

[bagder]

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.

[Zenju]

It seems CURLOPT_CUSTOMREQUEST "MLSD" is needed to reproduce

[bagder]

Not quite. But it seems a directory listing is needed!