On Thursday, February 20, 2003, at 09:32 PM, Bill Bumgarner wrote:
On Thursday, Feb 20, 2003, at 22:35 US/Eastern, Ben Hines wrote:
Apple's curl is more than two years old (!) Fink never even had such
an old perl, we started at 7.8.1 in Aug 2001.
That may be true. If Fink relies upon behavi
On Thursday, Feb 20, 2003, at 22:35 US/Eastern, Ben Hines wrote:
Apple's curl is more than two years old (!) Fink never even had such
an old perl, we started at 7.8.1 in Aug 2001.
That may be true. If Fink relies upon behavior in the "modern" curl--
my later message indicates there is still so
On Thursday, February 20, 2003, at 09:06 AM, Bill Bumgarner wrote:
[bumbox:/tmp] bbum% /usr/bin/curl --version
curl 7.7.2 (powerpc-apple-darwin6.0) libcurl 7.7.2 (OpenSSL 0.9.6b)
[bumbox:/tmp] bbum% /sw/bin/curl --version
curl 7.10.3 (powerpc-apple-darwin6.4) libcurl/7.10.3 OpenSSL/0.9.7
ipv6
On Thursday, Feb 20, 2003, at 12:14 US/Eastern, Alexander Hansen wrote:
But you do have curl-ssl installed, which will give you /sw/bin/curl .
Oh, duh! Yes.
---
This SF.net email is sponsored by: SlickEdit Inc. Develop an edge.
The most com
But you do have curl-ssl installed, which will give you /sw/bin/curl .
On Thu, 2003-02-20 at 12:06, Bill Bumgarner wrote:
> On Thursday, Feb 20, 2003, at 11:37 US/Eastern, Martin Costabel wrote:
> > On jeudi, fév 20, 2003, at 14:58 Europe/Paris, Bill Bumgarner wrote:
> > []
> >> Right. Your words
On Thursday, Feb 20, 2003, at 11:37 US/Eastern, Martin Costabel wrote:
On jeudi, fév 20, 2003, at 14:58 Europe/Paris, Bill Bumgarner wrote:
[]
Right. Your words make perfect sense, the situation does not.
Have you tried this with /usr/bin/curl instead of Fink's curl? Does it
behave in the sa
On jeudi, fév 20, 2003, at 14:58 Europe/Paris, Bill Bumgarner wrote:
[]
Right. Your words make perfect sense, the situation does not.
Bill,
Have you tried this with /usr/bin/curl instead of Fink's curl? Does it
behave in the same way?
--
Martin
---
On Thursday, Feb 20, 2003, at 02:01 US/Eastern, Martin Costabel wrote:
Bill Bumgarner wrote:
[]
I would think that answering 'n' -- disabling passive -- would work
much better with firewalls. It is certainly a requirement for NAT
translating routers (airport base stations and cable/dsl router
Bill Bumgarner wrote:
[]
I would think that answering 'n' -- disabling passive -- would work much
better with firewalls. It is certainly a requirement for NAT
translating routers (airport base stations and cable/dsl routers,
included).
This is the world upside down. You are the first person
On Wednesday, Feb 19, 2003, at 20:38 US/Eastern, Ben Hines wrote:
Use passive mode FTP transfers (to get through a firewall)? [Y/n]
'n' to this question and it fixed the problem. That seems
counter-intuitive.
curl -P is the command to disable PASV, and use PORT instead:
man curl "-P
On Wednesday, February 19, 2003, at 01:02 PM, Bill Bumgarner wrote:
curl -P - -f -L -s -S -O
ftp://www-126.ibm.com/pub/jikes/1.18/jikes-1.18.tar.bz2
and now it works fine. I see that NOT setting 'ProxyPassiveFTP'
should do the same, but it appears not.
Actually, I just did a 'fink
I'm behind a NAT'ing non-proxying firewall and I could not update jikes
because the download failed. Specifically, this...
curl -f -L -s -S -O
ftp://www-126.ibm.com/pub/jikes/1.18/jikes-1.18.tar.bz2
... failed.
I modified NetAccess.pm such that the above became
curl -P - -f -L -s
12 matches
Mail list logo
