rahul kumar wrote:
The thing is that i can't execute that command (wget Command)through
Windows...RUN Utility. So could you please give me some idea what i
need to do such that i can execute my Batch Application through
Windows XP Operationg System...
Wget it is a console-only command, so if
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hello all,
The GNU Project has appointed me as the new maintainer for wget, to fill
the shoes that Mauro Tortonesi is leaving. I am very excited to be able
to take part in the development of such a terrific and useful tool. I've
certainly found it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Tue, 26 Jun 2007, Micah Cowan wrote:
The GNU Project has appointed me as the new maintainer for wget
Welcome!
Speaking of licensing changes, I don't see a specific exemption clause
for linking wget with OpenSSL
Mishari Al-Mishari wrote:
Hi,
I am using the following command:
wget -p url
the url has frames.
the url retrieves a page that has set of frames. But wget doesn't
retrieve the html pages of the frames urls. Is there any bug or i am
missing something?
Works fine for me. In fact, if the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mauro Tortonesi wrote:
On Tue, 26 Jun 2007 13:33:35 -0700 Micah Cowan [EMAIL PROTECTED]
wrote:
- Wget should not be attempting basic authentication before it
receives a challenge (which could be digest or what have you). This
is a security
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Mauro Tortonesi wrote:
On Tue, 26 Jun 2007 13:33:35 -0700 Micah Cowan [EMAIL PROTECTED]
wrote:
i am not so sure this is a critical point. as hrvoje pointed out,
basic authentication is definitely the most used
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mishari Al-Mishari wrote:
Hi,
when i run this command
wget -p wwwladultfriendfinder.co
I recvd the following error messages, eventhoug I was able to
sucessfully download the page using the browser;
Resolving wwwladultfriendfinder.com...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Nick Lewis wrote:
Dear Wget
I am trying to use wget with a site that uploads a file and copies it
to the specified subdirectory but the file is not included in the
post. The command used is as follows:
wget --post-data=directory=images
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthew Woehlke wrote:
http://www.mail-archive.com/wget@sunsite.dk/msg06979.html
Did this patch make it into the soon-to-be-released version (1.10.3?)? I
need to wget a webpage that wants authentication, and I don't want to
have to put it on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi folks,
I've experimentally started a #wget channel for discussion and support,
at FreeNode (irc.freenode.net). Please feel free to come and lurk!
Without it having been announced, and only being open over this weekend,
a couple of people
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ben Galin wrote:
On Jun 26, 2007, at 11:50 PM, Micah Cowan wrote:
After running
$ wget -H -k -p http://www.fdoxnews.com/
It downloaded all of the relevant files. However, the results were still
not viewable until I edited the link
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
PLEASE NOTE: as of this moment, the repository at svn.dotsrc.org will no
longer be used for active development. Instead,
svn://addictivecode.org/wget/ will be used.
You can switch over your existing repositories using the command:
svn switch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roman Golovanov wrote:
Hi,
I've download a large file from unstable ftp server, so I use -c -T
10 for resuming download. But while resuming, WGET doesn't call CWD
to change remote directory, so FTP server cannot find file because it
search it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher G. Lewis wrote:
OK -
(First of all, welcome to Micah - thanks for working with us :-)
My pleasure! :-)
Sorry I didn't catch this earlier, but it looks like something broke
in the dev branch recently.
I've got a batch
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Christopher G. Lewis wrote:
I've got a batch that autobuilds the SVN dev tree and posts the
results to my windows wget page. Part of that build is to grab the
cacert.PEM from the curl site.
Recently, the SRC\WGET.EXE
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rich Cook wrote:
So forgive me for a newbie-never-even-lurked kind of question: will
this fix make it into wget for other users (and for me in the future)?
Or do I need to do more to make that happen, or...? Thanks!
Well, I need a chance to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
What is the status of the wget-patches list: is it being actively
used/monitored? Does it still serve its original purpose?
A brief glance at the archives seems to suggest that, for one reason or
another, it may be suffering a larger spam problem
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
What is the status of the wget-patches list: is it being actively
used/monitored? Does it still serve its original purpose?
Mauro and I are subscribed to it. The list served its
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
From various:
[...]
char filecopy[2048];
if (file[0] != '') {
sprintf(filecopy, \%.2047s\, file);
} else {
strncpy(filecopy, file, 2047);
}
[...]
It should be:
sprintf(filecopy,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've asked sunsite for a list to receive subversion commit
notifications, mainly so we keep our lists on the same site.
I haven't had a heckuvalot of luck in getting responses from them, so
far, and I'd really like to have the list set up right
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
This will receive all commit notifications, and is intended for devs to
be aware of what everyone is working on. I'm thinking about having
changes that just hit the trunk or the release branches (that is,
everything
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
On http://www.gnu.org/software/wget/wgetdev.html, step 1 of the summary is:
1. Change to the topmost GNU Wget directory:
% cd wget
But you need to cd to either wget/trunk or the appropriate version
subdirectory
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Fri, 6 Jul 2007, Micah Cowan wrote:
I forgot to mention that the wget-notify list is writable, as it's
also intended to permit discussion of development as it is happening.
So the svn notify list is effectively
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
The “Report a Bug” section of http://www.gnu.org/software/wget/ should
encourage submitters to send as much relevant information as possible
including wget version, operating system, and command line. The
submitter should also
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
Micah Cowen wrote:
Actually, the wget directory is the trunk in that example, since it was
checked out with
$ svn co svn://addictivecode.org/wget/trunk wget
Checking out the code using trunk is only one of three examples.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Tony Lewis wrote:
Micah Cowen wrote:
Actually, the wget directory is the trunk in that example, since it was
checked out with
$ svn co svn://addictivecode.org/wget/trunk wget
Checking out the code using trunk is only one
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Tony Lewis wrote:
The “Report a Bug” section of http://www.gnu.org/software/wget/ should
encourage submitters to send as much relevant information as possible
including wget version, operating system, and command line
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The wget-notify mailing list
(http://addictivecode.org/mailman/listinfo/wget-notify) will now also be
receiving notifications of bug updates from GNU Savannah, in addition to
subversion commits.
- --
Micah J. Cowan
Programmer, musician,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The sunsite.dk-hosted secondary web site will be redirecting to
http://www.gnu.org/software/wget shortly; I did not want the hassle of
maintaining two separate sites, especially when it did not appear that
they served different purposes.
The GNU
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Micah Cowan wrote:
The sunsite.dk-hosted secondary web site will be redirecting to
http://www.gnu.org/software/wget shortly; I did not want the hassle of
maintaining two separate sites, especially when it did not appear
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Micah Cowan [EMAIL PROTECTED]:
Must be just in the README. Anywhere else that anyone knows of, speak up! :)
In my memory it used to be the other way around ;-)
http://wget.sunsite.dk/ was the primary
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthew Woehlke wrote:
Micah Cowan wrote:
The wget-notify mailing list
(http://addictivecode.org/mailman/listinfo/wget-notify) will now also be
receiving notifications of bug updates from GNU Savannah, in addition to
subversion commits
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I would like for devs to be able to avoid the hassle of posting
non-trivial changes they make to the wget-patches list. To my mind,
there are two ways of accomplishing this:
1. Make wget-patches a list _only_ for submitting patches for
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
To group: It seems to me that the questions I'm asking Chris right now
are going to be common ones, unless we change the trunk Wget's version
to give some indication as to when its last update was performed.
We could use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Noèl Köthe wrote:
Am Montag, den 09.07.2007, 11:57 -0700 schrieb Micah Cowan:
Hello,
The sunsite.dk-hosted secondary web site will be redirecting to
http://www.gnu.org/software/wget shortly; I did not want the hassle of
maintaining two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Someone just asked on the #wget IRC channel if there was a way to
exclude files with certain names, and I recommended -X, without
realizing that that option excludes directories, not files.
My question is: why do we allow users to exclude
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Noèl Köthe wrote:
Hello,
I got a translated wget.1 manpage into russian.
I think translations should go into the upstream releases so everybody
profits from this. The question is now how should the translator submit
such a translation?
The
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hi all,
Effective immediately, messages sent to wget-notify will have the
Reply-To header set to wget@sunsite.dk. I am abandoning the earlier
idea of combining commit notifications with discussion threads _on_
those notifications. I still want to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
The following bug was submitted to Debian's bug tracker.
I'm curious what people think about this suggestion.
Don't we already check for something like redirected output (and force
the progress indicator to dots)? It seems to me that if that is
authentication
Date: Wed, 11 Jul 2007 17:54:44 +0200
From: Claus Alboege [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
Organization: Dotsrc.org - Open Source Hosting
To: Micah Cowan [EMAIL PROTECTED]
CC: [EMAIL PROTECTED]
References: [EMAIL PROTECTED]
q:res
Hi,
Micah Cowan [EMAIL PROTECTED] writes:
Would
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I've been keeping a schedule to organize what needs to get done and when
I expect things to be done by. It's been a rough schedule; however, I
believe it's complete enough to reveal now, along with an announcement
regarding the expected release date
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mauro Tortonesi wrote:
Micah Cowan ha scritto:
Update of bug #20323 (project wget):
Status: Ready For Test = In
Progress
___
Follow-up Comment #3
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
Noèl Köthe wrote:
A switch to the new GPL v3 is a not so small change and like samba
(3.0.x - 3.2) would imho be a good reason for wget 1.2 so everybody
sees something bigger changed.
There already was a version 1.2
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Admiral Markets wrote:
Bug-wget,
Ваш запрос принят и один из операторов просмотрит его и соответственно
ответит. Ниже приведена информация относительно вашего запроса. Пожалуйста,
при дальнейшей переписке не изменяйте идентификатор запроса в
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Joshua David Williams wrote:
URL:
http://savannah.gnu.org/bugs/?20466
...
Details:
This patch forces the --no-directories option if we're not actually keeping
the files we're downloading (as in the --delete-after and --spider options).
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rich Cook wrote:
On OS X, if a filename on the FTP server contains spaces, and the remote
copy of the file is newer than the local, then wget gets thrown into a
loop of No such file or directory endlessly. I have changed the
following in
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christian Roche wrote:
Hi there,
Hi!
please find attached two small patches that could be
considered for wget (against revision 2276).
patch-utils changes the file renaming mechanism when
the -nc option is in effect. Instead of trying to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
Consider this example, which happens to be how I realised this problem:
wget http://www.mxpx.com/ -r --base=.
Here, I want the entire site to be downloaded with each link pointing
to the local file. This works for some
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rich Cook wrote:
On Jul 13, 2007, at 12:29 PM, Micah Cowan wrote:
sprintf(filecopy, \%.2047s\, file);
This fix breaks the FTP protocol, making wget instantly stop working
with many conforming servers, but apparently start working
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Roman Shiryaev wrote:
hi,
I've just checkout the latest version from SVN and discovered changes
in wget's behavior when downloading files from one of our local web
servers. wget loops and cannot get file.
Hello, and thanks for the heads-up.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jaymz Goktug YUKSEL wrote:
Hello everyone,
I have a php code that processes only one unit at a time, because if I
process all 650 units, it time outs. So when I try to run the program
with WGET, I go like
process.php?no=0
and when
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 7/16/07, Dax Mickelson [EMAIL PROTECTED] wrote:
I've read the man page about 10 times now and I'm sure this issue is my
own stupidity but I can't see where or how.
[..]
Thus I would expect to get a directory full of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
I would like for devs to be able to avoid the hassle of posting
non-trivial changes they make to the wget-patches list. To my mind,
there are two ways of accomplishing this:
1. Make
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
From: Josh Williams
As far as I can tell, there's nothing in the man page about it.
It's pretty well hidden.
-e robots=off
At this point, I normally just grind my teeth instead of complaining
about the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
Micah Cowan wrote:
The manpage doesn't need to give as detailed explanations as the
info manual (though, as it's auto-generated from the info manual,
this could be hard to avoid); but it should fully describe
essential
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
Micah Cowan wrote:
Don't we already follow typical etiquette by default? Or do you
mean that to override non-default settings in the rcfile or
whatnot?
We don't automatically use a --wait time between requests. I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
I think we should either be a stub, or a fairly complete manual
(and agree that the latter seems preferable); nothing half-way
between: what we have now is a fairly incomplete manual
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
I don't know. The reason directories are matched separately from
files is because files often *don't* match the pattern you've chosen
for directories. For example, -X/etc should
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Wed, 18 Jul 2007, Micah Cowan wrote:
The manpage doesn't need to give as detailed explanations as the info
manual (though, as it's auto-generated from the info manual, this
could be hard to avoid); but it should fully
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Håkan Waara wrote:
Hello all,
I was looking for a small/fast HTML parser and came across wget's.
Since I prefer to not include all of wget's headers just for this, I
patched it to build 100% standalone. All that was needed was to
redefined
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Alright, so this message sums up what I understand about the way HTTP
authentication currently works, how I think it should work, and what I'm
intending to do as a stop-gap fix for 1.11.
HOW IT WORKS NOW:
As I understand it, --user and --password
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Christopher G. Lewis wrote:
Micah et al. -
Just for an FYI - the whole texi-info, texi-html and
(texi-rtf-hlp) is *very* fragile in the windows world. You actually
have to download a *very* old version of makeinfo (1.68, not even on
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I know this topic has been discussed before, but AFAICT it didn't really
get far. Neither side presented particularly compelling arguments
(IMHO), and so the burden of proof in arguing for change was not met.
==
Here are the reasons why I think
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
- Automated packaging and package-testing
What packaging does this refer to exactly?
Distribution tarballs. Automake has extremely good built-in creation and
testing
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Himanshu Gupta wrote:
Hi,
Hi!
Can somebody please point me to a document, which could provide me an
overview of the classes in source code. I've downloaded the code and
have no idea of how to go about reading the code.
I warmly welcome any
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Tony Lewis wrote:
In addition to whatever Josh and Micah told you, let me add the
information that follows. More than once I have had to relearn how wget
deals with command line options. The last time I did so, I created the
HOWTO that appears
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Maciej W. Rozycki wrote:
Otherwise it looks OK, I think. Though I am not sure whether it is
really needed given that many years have passed and nobody wanted such a
feature. But the decision is up to the maintainer (once you sort out
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Maciej W. Rozycki wrote:
On Wed, 25 Jul 2007, Matthew Woehlke wrote:
I both dislike GNU formatting and am not familiar with it, so obviously
someone that understands it will have to fix this.
Well, chances are nobody could be bothered to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Martin MOKREJŠ wrote:
Hi,
in the following you can see my proxy was not used only for the first
connect, in the remaining two cases data got copied through proxy
10.8.0.1:3128.
Thanks for this; filed in Savannah:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
From: Martin MOKREJÅ
I think the following happens due to a bug in wget unable to look
into a subdirectory for the file to be restarted in download:
[...]
Is this the same problem as this?:
Looks to be. Slated
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
A bug report made to Savannah
(https://savannah.gnu.org/bugs/index.php?20496) detailed an example
where wget would download a recursive fetch normally, but then when run
again (with -c), it would eat up vast (_vast_) amounts of memory, until
finally
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
A bug report made to Savannah
(https://savannah.gnu.org/bugs/index.php?20496) detailed an example
where wget would download a recursive fetch normally, but then when run
again (with -c), it would eat up vast (_vast_) amounts
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthias Vill wrote:
I just converted some project and a log-html was created with 6MB in
size and I agree to you, that this is a rare case and opening this file
with a browser is no fun, but still I don't like hardcoded sizes.
Maybe there will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
I agree that it's probably a good idea to move HTML parsing to a model
that doesn't require slurping everything into memory;
Note that Wget mmaps the file whenever possible, so it's
Hrvoje Niksic wrote:
mmap() isn't failing; but wget's memory space gets huge through the
simple use of memchr() (on '', for instance) on the mapped address
space.
Wget's virtual memory footprint does get huge, but the resident memory
needn't.
Sorry, I should've been clearer: specifically,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Hrvoje Niksic wrote:
Micah Cowan [EMAIL PROTECTED] writes:
Actually, I was wrong though: sometimes mmap() _is_ failing for me
(did just now), which of course means that everything is in resident
memory.
I don't understand why mmapping
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
According to the documentation for -nc, -r without -N or -nc will
overwrite existing files, but this appears not to be the case, since at
least 1.10.2. Was this intentional? That is, should the code, or the
documentation, be updated to fix this?
-
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
I have a question: why do we attempt to generate absolute paths and such
and CWD to those, instead of just doing the portable string-of-CWDs to
get where we need to be? Technically, we can violate the RFCs
(specifically, RFC 1738, which defines the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Daniel Stenberg wrote:
On Fri, 3 Aug 2007, Micah Cowan wrote:
I have a question: why do we attempt to generate absolute paths and
such and CWD to those, instead of just doing the portable
string-of-CWDs to get where we need to be?
Just
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Someone recently reported an inability to specify the prefix for libssl.
It seems the culprit is somehow the multiple invocation of the macro
AC_LIB_HAVE_LINKFLAGS, even though they appear in exclusive conditional
sections.
If one removes the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andra Isan wrote:
I am wondering if there is a way that I can download pdf files and
organize them in a directory with Wget or should I write a code for that?
If I need to write a code for that, would you please let me know if
there is any
containing papers that those authors have written. (one directory for
each author)
I am not sure if I can do it with Wget or not.
*/Micah Cowan [EMAIL PROTECTED]/* wrote:
I don't think your request is very clear. Certainly you can download PDF
files with Wget. What do you mean by organize them
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gnulib seems to have a module for doing exactly what we require:
prompting for passwords from a tty, including support for Windows. The C
code is at:
http://cvs.savannah.gnu.org/viewvc/gnulib/lib/getpass.c?root=gnulibview=markup
Gnulib actually
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Steven M. Schweda wrote:
From: Micah Cowan
[...]
Gnulib actually has quite a large number of modules designed for
portability; I imagine we could benefit from several of them.
Well, yeah, where portability is limited to various UNIX-like
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Andra Isan wrote:
I am wondering how can I download downloaded files into specified
directory by the user. For example, I dont want to save the downloaded
files into current directory.
Hi Andra. Check out the -P option.
- --
Regards,
Micah J.
Hi Roldan,
I'm forwarding this question to the wget mailing list, so you can
potentially reap the benefit of multiple, wget-experienced minds.
-Micah
Original Message
Subject: using wget for building web connectivity graph
Date: Sun, 12 Aug 2007 01:31:29 -0400
From: Roldan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Brian Keck wrote:
Hello,
Sometimes -p doesn't work. For instance:
wget -p http://en.wikipedia.org/wiki/Herbig-Haro_object
Hi,
The --debug flag will often provide useful information about why wget
doesn't download something you expect
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ed wrote:
On Mac OS X the (sanitised) log output looks like this
--16:56:33-- http://xx.blogs.com/xx/2007/03/carbon_offsets.html
= `/dirnames/xx.blogs.com/prawfsblawg/2007/03/carbon_offsets.html'
Resolving xx.blogs.com... 1.2.3.4
Matthew Woehlke wrote:
Micah Cowan wrote:
Brian Keck wrote:
Sometimes -p doesn't work. For instance:
wget -p http://en.wikipedia.org/wiki/Herbig-Haro_object
In this case, it appears that you've bumped into the fact that wget, by
default, will refuse to cross hostname boundaries
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Rudy Rusli wrote:
One of our clients are trying to connect to our server with digest
authorization and they are having problems. It returns 401 error code.
They are using WGET.
My coworker tests it using WSHARK and it seems that WGET tries BASIC
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Matthias Vill wrote:
Should --spider imply --recursive?
I guess many people expect it to behave that way (and therefore I think
it is a good idea that the output complains on not using --recursive,
but still some may want to have a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Jochen Roderburg wrote:
Zitat von Mauro Tortonesi [EMAIL PROTECTED]:
here is a table resuming the behaviour of current wget version (soon to be
1.11) and wget 1.10.2 regarding HTTP HEAD requests. i hope the table will be
useful to determine
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Mauro Tortonesi wrote:
anyway, to change wget's logic as you request, i just commited this patch
into the b20323 branch:
snip
Thanks for that.
Also, I'm not understanding why we send HEAD, ever, if we specify -O.
Are the semantics of -O
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
Index: src/spider.c
===
--- src/spider.c (revision 2336)
+++ src/spider.c (working copy)
@@ -67,7 +67,7 @@
};
static bool
-in_url_list_p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray Davison wrote:
WGET 1.10, 070817 cannot find IINTL6I.
What is it? I don't find any reference to it anywhere else.
Hi Ray,
I think we're going to need a little more information/context about what
you're trying to do and what happened, to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Ray Davison wrote:
Micah Cowan wrote:
Ray Davison wrote:
WGET 1.10, 070817 cannot find IINTL6I.
What is it? I don't find any reference to it anywhere else.
Hi Ray,
I think we're going to need a little more information/context about
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
It appears that some people (including myself) are confused by the fact
that wget will download files that match a rejection pattern (or fail to
match an accept pattern), if the file type is text/html.
The manual says:
Note that these two
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Micah Cowan wrote:
Is there any real reason that we can't just always reject files if they
match the reject list? Or, would it be worth adding an extra option to
allow even HTML files to be skipped?
It may be worth mentioning at this point
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Josh Williams wrote:
On 8/22/07, Micah Cowan [EMAIL PROTECTED] wrote:
What would be the appropriate behavior of -R then?
I think the default option should be to download the html files to
parse the links, but it should discard them afterwards
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA256
Gisle Vanem wrote:
The same happens on the 2nd, 3rd.. retry.
It seems there's an issue with the HEAD request. Maybe some
servers doesn't like it? Can anybody on Win32 try the above url?
All this is with a fresh SVN checkout. Built on MingW.
1 - 100 of 506 matches
Mail list logo
