FTP wildcards

Hello. I'd like to download all archive files wn16pcm.r[0..9][0..9] from the directory on ftp server but wget --passive-ftp ftp://ftp.ims.uni-stuttgart.de/pub/WordNet/1.6/wn16pcm.r* doesn't work and I cannot find what is wrong. Any advice appreciated. Please send CC of your reply - I'm not

Connexion refused.

I'm french so i do short : wget http://www.adc.com/News_Room/Breaking_News/index.jsp or wget http://www.adc.com/News_Room/Breaking_News/index.jsp-U Mozilla --04:40:33-- http://www.adc.com/News_Room/Breaking_News/index.jsp = `www.adc.com/index.jsp'Connect www.adc.com:80...Connect

gopher support?

Hi, some days ago I sent a Gopher patch to the wget-patches mailing list, but I got no reply. I thought that this could last some time but between submitting my patch and today there are 3 new CVS commits ... hm... not interested in adding the Gopher feature to wget or should I still wait some

Re: FTP wildcards

On Fri, 17 May 2002 11:24:25 +0100, Ian Abbott [EMAIL PROTECTED] wrote: On Fri, 17 May 2002 08:34:27 +0200, Jan Klepac [EMAIL PROTECTED] wrote: I'd like to download all archive files wn16pcm.r[0..9][0..9] from the directory on ftp server but wget --passive-ftp

wget -r and JavaScript

Hi all, is there a chance to let wget retrieve pages linked by JavaScript? Currently I don't manage to download e.g. a href=inside.phtml?page=area1 onClick=se tButton('image1') target=index onMouseOver=turnOn('image1','Area');return true onMouseOut=turnOff('imag e1'); or a

Re: gopher support?

On Fri, 17 May 2002 12:41:21 +0200, Stephan Beyer [EMAIL PROTECTED] wrote: not interested in adding the Gopher feature to wget or should I still wait some time? I have no objections to adding gopher support, but it's up to the main developer (Hrvoje Niksic) whether it ends up in GNU Wget. I

can't download

Hello. Any ideas why I cannot download files located at http://www.rotfl.prv.pl/ ? wget -A jpg -r http://www.rotfl.prv.pl/ downloads only index.html but wget -A jpg -r http://www.rotfl.prv.pl/some_file.jpg downloads this file... Bartek M. -- _ # Bartosz Maruszewski [EMAIL

question about wget flavor

Hello wget, $ wget -v wget: missing URL Usage: wget [OPTION]... [URL]... Try `wget --help' for more options. [root@rmt-gw]1014# wget --version GNU Wget 1.8.1 script.sh: #!/bin/sh wget=/usr/local/bin/wget -t0 -nr -nc -x --timeout=20 --wait=61 --waitretry=120 $wget ftp://nonanonymous:[EMAIL

Re: question about wget flavor

On Fri, 17 May 2002 16:59:07 +0400, Pavel Stepchenko [EMAIL PROTECTED] wrote: #!/bin/sh wget=/usr/local/bin/wget -t0 -nr -nc -x --timeout=20 --wait=61 --waitretry=120 $wget ftp://nonanonymous:[EMAIL PROTECTED]/file1.zip sleep 60 $wget ftp://nonanonymous:[EMAIL PROTECTED]/file2.zip Why WGET

Re: bug report and patch, HTTPS recursive get

In message Re: bug report and patch, HTTPS recursive get, Ian Abbott wrote... Thanks again for the bug report and the proposed patch. I thought some of the scheme tests in recur.c were getting messy, so propose the following patch that uses a function to check for similar schemes. Thanks

Possible bug in URL decoding

Hi, I have tried to download this page [1] following the links. The initial page is saved correctly. But then this link [2] shall be loaded which results in this http-query [3]. The actual problem is that '%2F' is decoded to '@2F' (whereas e.g. '%5F' is correctly decoded to '_'). René PS: I

Assertion failed in wget-1.8.1, progress-bar related.

Hello wget hackers :) While mirroring Debian I killed wget, and when resuming the mirroring one of the files in the remote site 'shrunk' (correctly, it is updated daily). The problem is that, being the new size smaller than the old, wget doesn two things wrong: - First, it doesn't

OpenSSL license exception

The FSF people have agreed that we add the following exception to Wget's license to allow linking with OpenSSL. The lawyer blurb at the beginning of every source file that explains about the GPL now contains the following appendix: In addition, as a special exception, the Free Software

1.8.2 branch opened

Since we need to have a release because of the OpenSSL legalese, we can as well fix the most important (crashing) bugs in 1.8.1. I have opened a branch named `branch-1_8_2' where the 1.8.2-specific changes will be applied. Note that only bug fixes will be accepted for 1.8.2. No new features.