wget bombs on wildcard requests

[shane_evans@…]

See output:

"neopbook:~ neo$ wget ​ftp://ftp.at.kde.org/pub/kde/stable/3.3/contrib/Slackware/10.0/*.txt --09:38:52-- ​ftp://ftp.at.kde.org/pub/kde/stable/3.3/contrib/Slackware/10.0/*.txt

=> `.listing'

Resolving ftp.at.kde.org... 192.35.244.50 Connecting to ftp.at.kde.org[192.35.244.50]:21... connected. Logging in as anonymous ... Logged in! ==> SYST ... done. ==> PWD ... done. ==> TYPE I ... done. ==> CWD /pub/kde/stable/3.3/contrib/Slackware/10.0 ... done. ==> PORT ... done. ==> LIST ... Error in server response, closing control connection. Retrying."

It waits on "LIST ..." for a few minutes then repeats the attempt. Installed version is wget-1.9.1. This is the same as my Slackware machine which does not do this. The above output is an example. The same occurs for any wildcard request (ie. *.tgz etc...).

[mww@…]

I consider it a bad idea to execute

wget ​ftp://ftp.at.kde.org/pub/kde/stable/3.3/contrib/Slackware/10.0/*.txt

as the shell will resolve the "*.txt" expression, machting all .txt files in $PWD ...

When using your url (incl. the wildcard), wget complains: "Warning: wildcards not supported in HTTP."

[thomas+opendarwin@…]

I would be willing to bet this is a passive ftp issue. Shane, are you behind a firewall? If so, either configure it to allow active FTP sessions, or try adding this to your command-line:

--passive-ftp

My guess is that it isn't wildcard specific, but specific to any mirroring of multiple files from an ftp site. Let me know.

[mww@…]

after 5 month w/o a response, I hereby close this bug

[shane_evans@…]

Sorry for no response. I did not receive any email notification of activity/comments on the defect and quite honestly do not have the time to track every defect I raise for a given project.

I will try the recommended solution and either reopen or close depending on the outcome.

Thanks,

Shane

[shane_evans@…]

Adding --passive-ftp to options worked. Thanks.