Hi,
On 05.02.2014 23:35, Guenter wrote:
On 05.02.2014 00:18, Daniel Stenberg wrote:
On Tue, 4 Feb 2014, Guenter wrote:
I can re-create the problem also with the curl commandline:
curl -v -O ftp://skytraq:skytraq@60.250.205.31/ephemeris/Eph.dat
Is it curl's connect back to the new port that f
On 05.02.2014 00:18, Daniel Stenberg wrote:
On Tue, 4 Feb 2014, Guenter wrote:
I can re-create the problem also with the curl commandline:
curl -v -O ftp://skytraq:skytraq@60.250.205.31/ephemeris/Eph.dat
Is it curl's connect back to the new port that fails? When I try it, it
connects back fin
On Tue, 4 Feb 2014, Guenter wrote:
I can re-create the problem also with the curl commandline:
curl -v -O ftp://skytraq:skytraq@60.250.205.31/ephemeris/Eph.dat
Is it curl's connect back to the new port that fails? When I try it, it
connects back fine to the server but it never seems to receiv
Hi all,
I'm using a software [1] with a Skytraq gps device, and this code uses
internally libcurl for downloading AGPS data ...
the FTP download fails for me - probably Skytraq has meanwhile changed
their FTP server (now FileZilla server) and / or their firewall,
whatever ...
I can re-create t
On 2/9/11 4:37:17 PM, Daniel Stenberg wrote:
On Wed, 9 Feb 2011, Leo wrote:
STAT /
...
But still I'm curious if those Cyberduck logs help understand how it
connects to both sites seemingly automatically?
It works without doing PASV or EPSV when doing directory listings by
the STAT comman
On Wed, 9 Feb 2011, Leo wrote:
STAT /
...
But still I'm curious if those Cyberduck logs help understand how it
connects to both sites seemingly automatically?
It works without doing PASV or EPSV when doing directory listings by the STAT
command as shown up here. STAT sends contents over t
Thanks for the detailed analysis, Michael.
On 2/5/11 3:16:18 PM, Michael Wood wrote:
Have you tried "--ftp-port -" with the servers you need to talk to?
Are you always running this from the same client or are multiple
clients involved? If multiple clients are involved, then the firewall
on the
Hi
On 5 February 2011 21:23, Leo wrote:
[...]
> -About 15 servers that don't like EPSV were reported. curl tries to connect
> with EPSV, then switches to PASV after a 75 sec wait and either fails (as in
> my previous example) or connects. If EPSV is disabled, curl connects with no
> problems.
>
>
from that output, it wouldn't completely solve this
issue as it takes 75 seconds to fail anyway. That failure seems to be
network-related (like a firewall) and just about the only way to avoid
that problem is to not even try EPSV...
Hi,
I'm back with the EPSV vs PASV issue - thanks again D
On 1/20/11 8:58:48 AM, Daniel Stenberg wrote:
On Thu, 20 Jan 2011, Michael Wood wrote:
< 425 Data connection already open.
OK, so the server thinks there's nothing wrong with EPSV, but libcurl
couldn't connect, so when libcurl retried with PASV, the server says
"Hey! What are you doing? Yo
On Thu, 20 Jan 2011, Michael Wood wrote:
< 425 Data connection already open.
OK, so the server thinks there's nothing wrong with EPSV, but libcurl
couldn't connect, so when libcurl retried with PASV, the server says "Hey!
What are you doing? You already asked me to open a port for EPSV and
Hi
On 20 January 2011 05:37, Leo wrote:
[...]
> OK, here's an example of one such FTP server. curl can't connect without
> disabling EPSV: it waits for over a minute then fails. Cyberduck connects
> without problems, and so does curl with EPSV disabled.
>
> I'm on Mac OS X 10.5.8 with libcurl 7.1
On 1/19/11 2:07:46 PM, Daniel Stenberg wrote:
Thanks and I apologize for top-posting - just didn't pay attention.
I've been using curl for over 5 years already, never had any problems,
that's why I never really needed this group. :) It's been easy enough to
use to never require any assistance
On Wed, 19 Jan 2011, Leo wrote:
Right now I have several FTP servers to which any FTP client connects
instantly.
After reading your mail I realized you're here talking about connecting the
data connection, and I assume you mean in a passive manner.
libcurl will only connect to them instant
Thanks, Daniel!
That clarifies what happens under the hood. And, obviously, curl
connects perfectly to majority of servers.
However, I still wonder what to do from the practical point of view...
Right now I have several FTP servers to which any FTP client connects
instantly.
libcurl will
On Wed, 19 Jan 2011, Leo wrote:
By default, libcurl always tries EPSV first, then PASV. However, some FTP
sites don't like EPSV and it's impossible to connect unless you disable it.
Such servers are completely broken. libcurl attempts to disable EPSV when it
gets a problem with it and retries
Hi everyone,
I wonder what's the universal way of handling the following issue:
By default, libcurl always tries EPSV first, then PASV. However, some
FTP sites don't like EPSV and it's impossible to connect unless you
disable it.
On the other hand, there are FTP sites that demand EPSV and wo
17 matches
Mail list logo
