Re: wget2

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Maciej W. Rozycki wrote: > On Fri, 30 Nov 2007, Mauro Tortonesi wrote: > >> not really. because of its JIT compiler, Java is often as fast as C/C++, and >> sometimes even significantly faster. > > And GCJ can be asked to compile Java to native mach

Re: fnmatch and non-ASCII characters in .listing

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > A Wget user showed me an example of Wget misbehaving. Hrvoje, do you know if this is a regression over 1.10.2? I'm guessing the use of fnmatch() being locale-dependant isn't; what about the rest? And; do you think this is impor

Re: Content disposition question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Vill wrote: > Hi, > > we know this. This was just recently discussed on the mailinglist and I > agree with you. > But there are two arguments why this is not default: > a) It's a quite new feature for wget and therefore would brake > compatib

Re: https_proxy environment variable

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ugo Albarello Lopez de Mesa wrote: > Hi, > > The proxies section of the manual doesn't mention the use of https_proxy > environment variable when you're behind a Proxy and getting something > from a HTTPS connection. It looks like Hrvoje fixed this

Re: Bugs! [Re: Question re server actions]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: > Alan Thomas wrote: >> Thanks. I unzipped those binaries, but I still have a problem. . . . > >> I changed the wget command to: > >> wget --recursive --level=20 --append-output=wget_log.tx

Re: How to change the name of the output file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mauro Tortonesi wrote: > On Tuesday 20 November 2007 20:38:13 Micah Cowan wrote: > >> Be advised, though, that -O doesn't simply mean "make the name of the >> downloaded result `filename'"; it means "act as

Re: Mirroring a site on the Internet Archive

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On 12/7/07, Brian <[EMAIL PROTECTED]> wrote: >> For the life of me, I cannot convince wget to download an old copy of a >> website from the Internet Archive. I think the url within a url is somehow >> messing it up.. >> >> wget

Re: FTP mirroring copy large files unnecessarily

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Tim Fletcher wrote: > Hi, > > First of all, I'm not on the list, so if you would cc me on any > responses I would appreciate it. > > I'm using wget to mirror an ftp site. The problem I'm seeing is that > very large files are copied each time, even th

Re: Minor fix to solve problem in wget-1.10.2 incorrectly parsing the date when doing FTP gets

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Gladstone wrote: > Brief outline: > > When you do a wget from an ftp: url, it tries to copy over the last > modified date of the file (this is good). However, due to timezone > issues, the date that it gets can sometimes be in the future, and t

Re: Minor fix to solve problem in wget-1.10.2 incorrectly parsing the date when doing FTP gets

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Philip Gladstone wrote: > Micah Cowan wrote: >> -BEGIN PGP SIGNED MESSAGE- >> Hash: SHA1 >> >> Philip Gladstone wrote: >> >>> Brief outline: >>> >>> When you do a wget from an ftp:

Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, perhaps its time to come back to the question of differentiated exit codes from Wget. This may be a 1.12 question, or perhaps a 1.13 question, but at any rate, with 1.11 ready to go out the day, we perhaps have a little more time to discuss it in d

Re: Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 R Kimber wrote: > On Sun, 09 Dec 2007 21:13:32 +0100 > Hrvoje Niksic wrote: > >>> I disagree again. If wget did not download a file, no matter what >>> the reason, then it should not exit with zero. I have written >>> several scripts that utilize wge

Re: Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerard wrote: > On Sunday December 09, 2007 at 03:13:32 (PM) Hrvoje Niksic wrote: > >> Gerard <[EMAIL PROTECTED]> writes: >> In particular, if Wget chooses not to download a file because the local timestamp is still current, or because its s

Re: Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerard wrote: >> On December 09, 2007 at 04:19PM Micah Cowan wrote: > >> I believe I already answered this: it is because a non-zero exit status >> always means "something's wrong". Myriad scripts invoke utili

Re: Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Gerard wrote: >> On December 09, 2007 at 07:03PM Stuart Moore wrote: > >> Could the exit code used be determined by a flag? E.g. by default it >> uses unix convention, 0 for any success; with an >> --extended_error_codes flag or similar then it uses e

Re: Content disposition question

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Actually, the reason it is not enabled by default is that (1) it is >> broken in some respects that need addressing, and (2) as it is currently >&

Re: NEWS file

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > I've noticed that the NEWS file now includes contents that would > previously not have been included. NEWS was conceived as a resource > for end users, not for developers or distribution maintainers. (Other > GNU software seems

Re: Wget exit codes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 R Kimber wrote: > On Sun, 09 Dec 2007 13:19:51 -0800 > Micah Cowan wrote: > > >> I believe I already answered this: it is because a non-zero exit >> status always means "something's wrong". Myriad scripts

wget -Y0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 What's up with the -Y option? It doesn't appear in the manual (except in an example invocation, in the section on how to report bugs); but it does show up in --help: -Y, --proxy explicitly turn on proxy. --no-proxy

Re: Question about spidering

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Srinivasan Palaniappan wrote: > I am using WGET version 1.10.2, and trying to crawl through a secured > site (that we are developing for our customer) I noticed two things. > WGET is not downloading all the binaries in the website. It downloads > abo

Re: wget -Y0

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > -Y should probably just be removed. Okay. Thanks very much for your input; I think I'll do this, as it's probably the simplest fix, and seems appropriate if we want to encourage folks to use --no-proxy rather than -Y 0. - -- M

Re: Redirects across hosts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On Dec 12, 2007 1:54 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: >> Well, we already limit by refusing to cross host boundaries unless >> specifically asked (obviously _except_ in the case of redire

Redirects across hosts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A user on IRC was frustrated by the fact that Wget cannot be instructed not to follow redirects to different hosts. And I can see how this could be a problem for some. What do people think about an option to restrict redirect-following to only the app

Re: Redirects across hosts

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Josh Williams wrote: > On Dec 12, 2007 1:46 PM, Micah Cowan <[EMAIL PROTECTED]> wrote: >> And, what do you think about enabling that option by default when >> recursive mode is on? > > Well, I think it's obvious that

Re: Question about spidering

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: > Srinivasan Palaniappan wrote: >> wget -r l5 --save-headers --no-check-certificate https://www.mystie.com > ^^ > -r doesn't take an argument. Perhaps you wanted a -l before the 15? Or a - befo

libmd5, DOS/Windows

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 In order to avoid an issue where we #include the md5.h file from gnulib, but link against the one in Sun's library, the md5 code has been placed in a separate directory, md5/ (in mainline). The DOS and Windows Makefiles will probably need to be patched

Re: negative Content-Length: core dump

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robert Krauße wrote: > I was about to code a little web server for study reasons. > So I made a little mistake and sent a negative content > length field to my clients. > Tried to get a jpg file with wget and it dumped: > > [EMAIL PROTECTED]:~$ wget 1

Re: wget and encoding

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mishari Almishari wrote: > hi, > if the webpage is encoded in some encoding scheme, does the wget save > the webpage with the encoding or after decoding? What about if i used > the -E option, does is save it after decoding it to its original html > con

Re: seg fault ~30G

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Steven M. Schweda wrote: > From: Hunter > >> I'm getting a seg fault anytime I approach 30G in transfer with wget. >> >> I did a google search, but didn't see a resolution. Is there one I >> simply cannot find? > >It's hard to say. I'll tell yo

Re: wget not using max bandwidth

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Zanzaricchio B wrote: > I have a problem with wget that doesn't really use all the available > bandwidth... but let me explain a little bit more. > I tried to download files from other web sites with similar results. > Downloading gcc from GNU web s

Re: wget through proxy is slow (Connection:Keep-Alive ignored?)

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Yazeed Hamid wrote: > Hi to all. > Thank you very much for your efforts and a happy new year to all. > > I have been using wget in a bash script to measure website response > times over different proxy configurations. > > /usr/bin/time "%e Seconds"

Re: --transform-html option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jacobo Romero Manrique wrote: > Hi, > the diff attached is only a proof of concept since it's a quick hack, but is > working for my needs. > It adds an "--transform-html" option which specifies a shell command to use > as a preprocessor on the downl

Re: wget from hg repository and Solaris don't mix well --

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Townsend wrote: > = > The Solaris `sed' doesn't flush the last data line if that line isn't > terminated with a NEWLINE. The problem surfaces in the "po" directory > and the problem code is in the "Rules-quot" file where `msgfilter' > passes

wget@sunsite.dk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Perjan Moors wrote: > Hi there, > > I am trying to wget the URL > http://www.programmagids.nl/[EMAIL PROTECTED]&datum=2008-01-10 > > but it doesn't work. wget seems to shuffle around a bit with the %26 and > the & character, but in the end sends a ht

wget@sunsite.dk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Perjan Moors wrote: > > Perjan Moors wrote: Hi there, I am trying to wget the URL http://www.programmagids.nl/[EMAIL PROTECTED]&datum=2008-01-10 but it doesn't work. wget seems to shuffle around a bit with the %26 and >>>

wget@sunsite.dk

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > I that case I'm mistaken in reading the error output. > The problem still is: it doesn't get the same page my browser does, but > the default page that is displayed in case of faulty arguments. > If I open the page with my browser, I get the televis

Re: Filename trouble

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nichlas wrote: > Hi, i'm new to the list. > > I'm currently trying to download about 600 pdf's linked to from > individual HTML pages on a site. > > Problem is, that when the PDFs get downloaded, they get names like > > "B111009.pdf?rguid=C26A0D99-F

Re: Filename trouble

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Matthias Vill wrote: > Maybe also > --- > -O file > --- > is of some interest to you as it seems you are batch-fetching and maybe > know a good name in advance I was assuming that this: >>> I'm currently trying to download about 600 pdf's link

Re: Error with wget on AIX5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hopkins, Scott wrote: > All, > > I recently compiled wget 1.10.2 on one of our AIX 5.3 > machines, and it appeared to compile fine, after disabling nls. The > binary appears to be intact, and actually appears to make connections > out

Re: wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jochen Roderburg wrote: > Hi Michael, > > Just curious: what is now holding back a release of the 1.11 version? *sigh*, just waiting on the disclaimer from my employer. I actually really expect to get that finished up this week, though. I'm told that

Re: wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Christopher G. Lewis wrote: > Micah - > > I've been quite busy with work stuff (end of the year is killer for me) so > can you give me a quick update on what needs to be done for wget for 1.11 Codewise, zilch (unless Jochen brings something crucia

Re: wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jochen Roderburg wrote: > Hmm, these are "really strange cases" with some "really strange hosts" only. > Involved are content-disposition (again ;-) and redirection. Often wget > somehow > "loses" the Content-Length information and keeps on downloadin

Multiple connections to single host

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, RFC 2616 strongly suggests (but does not require) that only at most two persistent HTTP connections to a given host be maintained. However, note that this 1. Does not apply to non-HTTP connections (such as FTP) 2. Does not apply to non-persist

Re: Skip certain includes

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wayne Connolly wrote: > Hi, > > I am using wget on php pages to mirror dynamic mysql/php pages from a > staging server to a non-dynamic production server. > > Ie: > Staging Server A = Dynamic php/mysql > Production Server B = Flat rendered HTML in th

Re: Error with wget on AIX5.3

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > "Hopkins, Scott" <[EMAIL PROTECTED]> writes: > >> Interesting. Compiled that code and I get the following when running >> the resulting binary. >> >> /var/opt/prj/wget$ strdup_test >> 20001448 > > As I suspected. S

Re: wget from hg repository and Solaris don't mix well --

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paul Townsend wrote: >>> The Solaris `sed' doesn't flush the last data line if that line isn't >>> terminated with a NEWLINE. The problem surfaces in the "po" directory >>> and the problem code is in the "Rules-quot" file where `msgfilter' >>> passes

Re: Sym link following

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Wayne Connolly wrote: > Hi all, > > I love wget - so sweet. > > Anyway, i am testing this on http://staging.measanctum.com as the wget > dump target with this command: > > wget -m -nH -p -k --retr-symlinks http://measanctum.com > /srv/www/htdocs/sta

Re: [wget] large memory allocation with -r and large files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > When downloading large files in web directory (directory listing enabled), > with > wget -r http://example.com/folder/ > On Solaris with 512mb memory, wget fails with: > wget: realloc: Failed to allocate 1073741824 bytes; me

Release: GNU Wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 It gives me great pleasure to announce the release of GNU Wget 1.11 It's been over two years since the last release, 1.10.2, but we've made it. (Thanks mainly to the efforts of Wget's previous maintainer, Mauro Tortonesi - thanks Mauro!) The sourc

Future of Wget

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 So, I've been spending some time thinking about how I want to break things down in the next several versions of Wget. Here's a summary of how I think it'll break down; following it is a more in-depth discussion. 1.12 - Support for parsing links

Re: Release: GNU Wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Accidentally hit Reply instead of Reply-All) Willener, Pat wrote: > Are there any 1.11 executables available for any platforms? Not from us; we just release the source packages. I suspect that Noèl Köthe will probably have Debian unstable packages o

Re: installing wget

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nelly Mouawad wrote: > Hi, > > I would like to ask you about a problem I had while trying to install wget > on my machine. I have mandrake linux. > The problem comes from the fact that I am not administrator on my machine, > and I don't have write acc

Re: wget-1.11 assertion failed in ru_RU.UTF-8 locale

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Michael Shigorin wrote: > Hello Micah, > my friend has found[1] that wget-1.11 introduced a regression: > running it in ru_RU.UTF-8 locale results in failed assertion: > > LC_MESSAGES=ru_RU.UTF-8 wget -c > http://pgfoundry.org/frs/download.php/

Re: Release: GNU Wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Preetam Joshi wrote: > Apologies if posting on wrng link but i am badly in need of help. > > I am trying to use wget following is the syntax > > wget -d --proxy-user="someuser" --proxy-password="somepasswd" > http://10.16.0.35:80/www.google.com/ Yea

Re: Problems with progress on large files

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Slava S. Kardakov wrote: > Wget aborts on huge files: > > $ wget > 'http://bouncer.i-rs.ru/?product=OpenOffice.org&lang=ru&version=2.3.1&os=linuxinteltarball > >

Re: Release: GNU Wget 1.11

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Preetam Joshi wrote: > Hello Micah, > > Thanks for the help i just had one more query that is > > I have compiled the wget package by configuring it with ntlm option. > So does that mean i can get thru proxy servers which have ntlm > authentication.

Re: wget 1.11 no-clobber still sending GET request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles wrote: > Hi, > > Comparing the behavior of wget 1.11 and wget 1.10, in wget 1.11 using > wget -nc url still sends a GET request to the server while this does > not happen is wget 1.10. > > My question is how do I turn off this behavior? > >

Re: [PATCH] Reduce COW sections data by marking data constant

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Forgot to CC the list. Also, my mailer seems to be screwing up the quotes. :( -M) Diego 'Flameeyes' Pettenò wrote: | As for maintainability, while a character pointer is easier to handle than a | character array, modern compilers warns you if you

Re: [PATCH] Reduce COW sections data by marking data constant

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Of course, the changes that introduce const without compromising > maintainability, such as the constification of the Wp declaration in > ftp-opie.c, are more than welcome. Indeed. In fact, even if Diego doesn't submit a patch w

Re: [PATCH] Reduce COW sections data by marking data constant

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Note that you could also do all the pointer maths up-front, leaving >> existing usage code the same, with something like: >> >> static cons

Re: Feature: overlapped resume that compares last data

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Blargg wrote: > Feature idea: when resuming (continuing) on a partially-downloaded > file, resume slightly earlier than normal and compare with the local > copy, to ensure that it's the same file and that the server doesn't > handle resumption erroneou

Prerelease: Wget 1.11.1-b2080

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 A prerelease version of Wget 1.11.1 has been made available at: http://alpha.gnu.org/gnu/wget/wget-1.11.1-b2080.tar.gz http://alpha.gnu.org/gnu/wget/wget-1.11.1-b2080.tar.gz.sig (GPG signature) This version is believed to have addressed the follo

Repository [Re: Prerelease: Wget 1.11.1-b2080]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 This might be a good opportunity to point out that, as I'd promised previously, the Subversion repository is no longer being kept in-sync with changes made to Wget, starting from the release of 1.11. All further changes in the Wget 1.11.x line will be

Re: Prerelease: Wget 1.11.1-b2080

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: | Micah Cowan <[EMAIL PROTECTED]> writes: | |> Also: the fix to the locale/progress-bar issues resulted in the |> added use of a couple wide-character/multibyte-related functions, |> mbtowc and wcwidth. | |

Internationalization [Re: Prerelease: Wget 1.11.1-b2080]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: | As to wchar_t and mbtowc: I'm curious how many systems we're still | trying to support actually lack these, given that they've been around | since the very first C standard? Note that, as mentioned in the relea

Re: Wget and Socks Proxy Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bolee Menee wrote: > Hello, > > There is information about Socks Proxy support on official website: > >> Supports HTTP and SOCKS proxies > > But in reality there is no support and there is no much instructions how > to get it worked. Hm, yeah. I

Re: Internationalization [Re: Prerelease: Wget 1.11.1-b2080]

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Willener, Pat wrote: > Thanks - that's the right direction to go! > > There are still so many products out there that refuse to acknowledge > that multibyte / wide characters have been a necessity and reality > for a long time, and not supporting mult

Re: wget and sunsolve.sun.com

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Paul wrote: ... > I won't go into details, but wget is used to download files from > sunsolve.sun.com, which requires authentication. Up to wget v1.10.2 a > command like that worked fine: > > wget --http-user=xxx --http-passwd=yyy > "http://

Re: Wget and Socks Proxy Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: | I've not checked a more recent release but wget-1.10.2 has references to | both a; '--with-sox' and a '--with-socks' configure option but neither do | anything AFAICT. You mean in utils/README, right? Yeah, but that's talki

Re: Prerelease: Wget 1.11.1-b2080

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Also: the fix to the locale/progress-bar issues resulted in the >> added use of a couple wide-character/multibyte-related functions, >> mbtowc and

Re: Wget and Socks Proxy Support

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 After some more digging, it looks like I was wrong about the "socksified" Wget being something different from the official sources; according to the news file, socks support was introduced in Wget 1.4.0. I don't have access to 1.4 sources, but Wget 1.5

Re: Prerelease: Wget 1.11.1-b2080

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> Rather than disable NLS altogether if wcwidth or mbtowc are missing, >> I've opted to disable NLS support only for the progress bar itself: >

Re: Wget with mp3-streams - fades out...

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Bjornar Moltubakk wrote: > Hello, > > I've been using wget on my firewall/server (Clarkconnect box) for > several years to record mp3-audio streams (radio programs) coming from > an icecast server. I have made som very simple scripts that record the >

Re: wget and sunsolve.sun.com

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Martin Paul wrote: > Micah Cowan wrote: >> Is there no way to get the server to issue an authentication challenge? >> A browser would never send authentication credentials without first >> being challenged, which is part of why I

Re: download part of a website

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Paolo Lunazzi wrote: > Hi everybody! > I have a particular problem with wget because I've to > solve a strange requirement. > I would like to download, starting from the homepage > of a website, the first 100 pages found with a visit > of the link in a

Re: wget and sunsolve.sun.com

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: > Agreed. I may hate it, but the fact is that implicit, unasked-for > password authentication was "working" in 1.10.2, and there's no way to > get that behavior for 1.11, so it's a "lost feature&

Re: wget and sunsolve.sun.com

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Martin Paul <[EMAIL PROTECTED]> writes: > >> Micah Cowan wrote: >>> Then, how was --http-user, --http-passwd working in the past? Those only >>> work with the underlying HTTP a

Re: CS translation fix, p - bp->buffer <= bp->width assert

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Petr Koloros wrote: > Hi, > > someone obviously forgot about the three characters for 'eta' in Czech > translation. Without the following patch and with czech locale wget crashes > quite often. Hi, thanks for the patch; however, you'd probably have b

Re: CS translation fix, p - bp->buffer <= bp->width assert

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > Micah Cowan <[EMAIL PROTECTED]> writes: > >> The prerelease still has a potential for crashes: in the Czech locales >> it will tend to crash if the download is large (or slow) enough to push >> min

Re: [PATCH] Canonicalize both user and system wgetrc

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julien B. wrote: > Currently, when calling the initialize() function into init.c, before > to check if the user and system wgetrc point to the same location, no > canonicalization is done. > This results in leaving wget unable to follow links, or to un

Prerelease: GNU Wget 1.11.1-b2092

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 http://alpha.gnu.org/wget/ With this prerelease comes the following additional improvements: - - More minor improvements related to the progress bar in varied locales. - - Applied Hrvoje's patch dealing with fnmatch() stuff. - - Fixed an issue wher

Re: comments on using wget

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Anirban Banerjee wrote: > Hello everyone, > I am going to start a small project to analyze > how 8 websites are connected to each other and would be grateful for > any comments which people might have regarding the methodology I p

Re: Prerelease: GNU Wget 1.11.1-b2092

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: > http://alpha.gnu.org/wget/ Sorry, that should be http://alpha.gnu.org/gnu/wget/. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -BEGIN PGP SIGNATURE- Version: Gn

Re: Wget 1.11 on a IBM iSeries platform problems No Virus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 [EMAIL PROTECTED] wrote: > > Hello, > > I have compiled a GNU Wget 1.11 on a IBM iSeries platform. (Host system > type... powerpc-ibm-os400) > Well, wget works but I have some problems. > > 1) I need messages in spanish, but I´ve only in english. >

Re: Wget 1.11 on a IBM iSeries platform problems No Virus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Micah Cowan wrote: > [EMAIL PROTECTED] wrote: >> Hello, > >> I have compiled a GNU Wget 1.11 on a IBM iSeries platform. (Host system >> type... powerpc-ibm-os400) >> Well, wget works but I have some problems. > >&

Re: Wget 1.11 on a IBM iSeries platform problems No Virus

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hrvoje Niksic wrote: > I agree that clock_getres itself isn't important. Still, Wget needs > to choose a clock that actually works out of several possible clocks > allowed by POSIX (and common extensions), so it's advisable to at > least attempt to us

Re: Wget continue option and buggy webserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles wrote: > Hi, > > In wget 1.10, I observe this behavior: > > If I execute this command > > wget -c somefile > > where somefile is already fully retrieved, but for some reason (buggy > server), the webserver return a 400 OK HTTP message inste

Re: Wget continue option and buggy webserver

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Charles wrote: > The problem is that the server does not give error. Normal web server > like apache gives request range unsatisfied error if we try to request > range 1- for a file which size is 1 but this webserver give > HTTP 200 OK where wg

Re: Problem with password.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rene Maldonado wrote: > /usr/bin/wget -nc -x -nH > --directory-prefix=/var/local/Process/Data/CSFN/tmp/ -a /tmp/wgetFTP.log > ftp://myname:[EMAIL PROTECTED]@10.50.2.35/IN/ > How can I use the @ symbol on the password? Percent-encode it: p%40ssword.

Re: Option to limit number of files downloaded

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Julio wrote: > It would be nice to have another option to limit the size of the downloaded > files. When I get files, I am interested in html files and the thumbnails > (gif, > jpg). But sometimes there are bigger versions of the thumbnais (gif, jpg)

Re: Running W-get through a Proxy

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Stuart Davies wrote: > To whom it may concern. Hi Stuart, thanks for reposting to the list. > at 12:52 /EVERY:M,T,W,Th,F,S,Su D:\x-x\Auto\WGET\wget.exe > --user=XXX --password=YYY --directory-prefix="D:\Download" > --secure-protocol=auto > --

Re: execute option

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Rene Maldonado wrote: > Is possible to execute the move command on the host server after > transferring a file? > > What I need is to retrieve a file, and after transfer from the READY > directory, move it to a SENT directory on the host. I'm afraid

Re: Bug

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark Pors wrote: > Hi, > > I posted this bug over two years ago: > http://marc.info/?l=wget&m=113252747105716&w=4 >>From the release notes I see that this is still not resolved. Are > there any plans to fix this any time soon? I'm not sure that's a b

Re: Content-Disposition UTF-8 and filename problems

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd Pattist wrote: > I'll answer my own question for the record. > > It's the Content-Disposition: attachment; filename*=UTF-8''filename.zip > header that causes the problem. I set wget to use the Privoxy proxy > (wgetrc line): > > http_proxy = lo

Re: Accept and Reject - particularly for PHP and CGI sites

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Todd Pattist wrote: > I'm having trouble understanding how accept and reject work, > particularly in the context of sites that rely on CGI and PHP to > dynamically generate html pages. My questions relate to the following: > > 1) I don't fully unders

Re: Problem with wget (v1.11) and FTP URL including ..

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard wrote: > Hi, > > Since upgrading wget from 1.10.2 to 1.11 (on a Sun Solaris 9 server) I > am no longer able to retrieve files with a command similar to: > > wget --user=xxx --password=xxx --output-document=logfile.txt > ftp://ftp.username.myb

Re: Mirroring issues / help

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Aaron Griffin wrote: > Hey guys, > First off, I am not subscribed to the list, so please CC me to any > responses. > > I am having a little difficulty mirroring a drupal site using either > wget _or_ > httrack. Both give me the same results, which lea

Re: Mirroring

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Момчил Божинов wrote: > Hi, > > Im trying to mirror a website using wget (*GNU Wget 1.10.2*, a > non-interactive network retriever.) on Windows XP SP2 > > Here is what I use: > *wget -m -p -r -nH --cache=off --level=0 --cut-dirs=3 > **http://code.p

Re: Continue overlap verify

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Pooya Pourvaghar wrote: > some continued files (with -c option) downloaded incorrectly, usually > large ones. > I've read something about some buggy http servers here: > http://www.mail-archive.com/wget@sunsite.dk/msg10862.html > > It's good to add a

Re: Problem with wget (v1.11) and FTP URL including ..

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Richard wrote: > Hi Micah, > > I've tried to post this reply to the mailing list but it's getting > blocked by SpamAssassin so having to reply directly - hope that's OK. Sure; it's probably due to the "xxx" strings within URLs. :) I was thinking per

<    1   2   3   4   5   6   >