Bugs item #1378768, was opened at 2005-12-12 15:48
Message generated for change (Comment added) made by bagder
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1378768&group_id=976

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: ftp
>Group: bad behaviour
Status: Open
>Resolution: Invalid
>Priority: 3
Submitted By: Nobody/Anonymous (nobody)
Assigned to: Daniel Stenberg (bagder)
Summary: A few bugs

Initial Comment:
>From log:
E:\...\curl-7.15.1>curl -i 192.168.0.27 -u anon
ymous:passwd@ -T readme ftp://192.168.2.1/

Ц►{G‼Г4Ў_╤№№q % Total % Received % Xferd Average
Speed Time Time T
ime Current
                                 Dload Upload Total
  Spent Left Speed
  0 3046 0 13 0 0 260 0 --:--:--
--:--:-- --:--:-- 0
curl: (7) couldn't connect to host

E:\...\curl-7.15.1>

And here's a crash:

E:\...\curl-7.15.1>curl -u anonymous:passwd@ -T
 c:\temp\4\*.* ftp://192.168.2.1/ -P -

curl: (6) Could not resolve host: c:\temp\4\readme_; No
data record of requested type
curl: (6) Could not resolve host:
c:\temp\4\RELEASE-NOTES; No data record of requested type
*CRASH*
E:\...\curl-7.15.1>

Contents of c:\temp\4:
═══════════════════ C:\temp\4 ═════╤════════╤═════
s Name │ Size │ Date │Time
.. │< Up >│12.12.05│17:38
readme │ 3033│07.12.05│08:58
readme_ │ 3033│07.12.05│08:58
release-notes │ 2593│07.12.05│08:58

----------------------------------------------------------------------

>Comment By: Daniel Stenberg (bagder)
Date: 2005-12-14 21:08

Message:
Logged In: YES
user_id=1110

While we wait for feedback I modified some properties for
this report.

----------------------------------------------------------------------

Comment By: Dan Fandrich (dfandrich)
Date: 2005-12-13 00:32

Message:
Logged In: YES
user_id=236775

The garbage in the first example could be coming from the
http://192.168.0.27/ URL downloaded before the ftp upload.
The "Could not resolve host" messages in the second example
are likely from the file names treated as hosts due to shell
expansion. Except for the "*CRASH*" (if valid), it's not
clear that curl is doing anything wrong. I doubt the command
lines given are really what the user wants, though.

----------------------------------------------------------------------

Comment By: Daniel Stenberg (bagder)
Date: 2005-12-12 23:44

Message:
Logged In: YES
user_id=1110

What do you mean with crash, really?

What's the junk letters all over?

What do --trace logs show?

----------------------------------------------------------------------

You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=100976&aid=1378768&group_id=976
Received on 2005-12-14