RE: --http-passwd=cleartextpwd
Wow, that ws quick! Thank you. The man page proposes to put the password in wgetrc or another file. Your solution sounds more secure to me. Maybe someone has some time left to enhance the man pages. Bye, Berny -Original Message- From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] Sent: Dienstag, 27. Januar 2004 15:46 To: Voelker Bernhard Cc: '[EMAIL PROTECTED]' Subject: Re: --http-passwd=cleartextpwd Voelker Bernhard [EMAIL PROTECTED] writes: I recognized that the password passed to wget with the option --http-passwd= can be seen as clear text with tools like ps and top. Yes. I don't think there is a portable and reliable way to prevent this. You can work around it, though. Put your URLs with passwords to a file and invoke Wget with `wget -i FILE'. Or use `wget -i -' and type the URL followed by ctrl-d.
RE: [PATCH] implementation of determine_screen_width() for Window s
Works fine for me on Winnt 4.0 sp6a (cmd windows with column sizes != 80 now use the whole line for the progress bar), compiled with MSVC. A binary with that patch is available from http://xoomer.virgilio.it/hherold/ In order to test just open a command window with a buffer column size !=80, the progress bar now should use the whole line. Anyone who can test this on different platfroms (windows 95/98/ME/2000/XP) should please report to the list. Anyone who can compile this with different compilers (watcom, cygwin, mingw, borland) should please report to the list. If no problems arise I'd vote for inclusion in cvs. Note: for a complete look-and-feel similar to the unix version we still need a detection when the size changes (on unix this is done with received_sigwinch in bar_create and bar_update), if this is possible. Currently if the cmd window is resized on the fly (as a matter of fact the window buffer size, not the real window) the progress bar continues to use the old size. Still from a usability point of view this patch is already a lot better than the old behaviour (DEFAULT_SCREEN_WIDTH). Heiko -- -- PREVINET S.p.A. www.previnet.it -- Heiko Herold [EMAIL PROTECTED] -- +39-041-5907073 ph -- +39-041-5907472 fax -Original Message- From: David Fritz [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 28, 2004 4:33 AM To: [EMAIL PROTECTED] Subject: [PATCH] implementation of determine_screen_width() for Windows Attached is a small patch that implements determine_screen_width() for the Windows build. Cheers
Re: [PATCH] implementation of determine_screen_width() for Window s
[ This discussion is about a patch that determines the screen width on Windows console. ] Herold Heiko [EMAIL PROTECTED] writes: Note: for a complete look-and-feel similar to the unix version we still need a detection when the size changes (on unix this is done with received_sigwinch in bar_create and bar_update), if this is possible. Yes. Specifically, Unix's SIGWINCH simply sets a flag that means window size might have changed, please check it out. That is because checking window size on each refresh would perform an unnecessary ioctl. One thing we could do for Windows is check for window size every second or so.
RE: [PATCH] implementation of determine_screen_width() for Window s
From: Hrvoje Niksic [mailto:[EMAIL PROTECTED] .. Yes. Specifically, Unix's SIGWINCH simply sets a flag that means window size might have changed, please check it out. That is because checking window size on each refresh would perform an unnecessary ioctl. One thing we could do for Windows is check for window size every second or so. I agree, but I have no idea how taxing those GetStdHandle() and GetConsoleScreenBufferInfo() are. Maybe David can shed more light on this, or even profile a bit. Possibly the handle could be cached, saving at least the GetStdHandle() bit. Heiko -- -- PREVINET S.p.A. www.previnet.it -- Heiko Herold [EMAIL PROTECTED] -- +39-041-5907073 ph -- +39-041-5907472 fax
Re: wget crashes when working on large files
This is a bug -- regardless of whether it supports large files or not, Wget shouldn't crash when dealing with them. I plan to look into large file support for the next version of Wget.
Re: Feature request: execute command after download complete
It sounds to me like you could do the equivalent with a simple shell script. For example: while read url do wget --limit-rate=2k $url # Your commands go here. done URL-LIST-FILE
Re: [PATCH] implementation of determine_screen_width() for Windows
Herold Heiko wrote:
From: Hrvoje Niksic [mailto:[EMAIL PROTECTED]
..
Yes. Specifically, Unix's SIGWINCH simply sets a flag that means
window size might have changed, please check it out. That is
because checking window size on each refresh would perform an
unnecessary ioctl.
One thing we could do for Windows is check for window size every
second or so.
I agree, but I have no idea how taxing those GetStdHandle() and
GetConsoleScreenBufferInfo() are.
Maybe David can shed more light on this, or even profile a bit.
Possibly the handle could be cached, saving at least the GetStdHandle() bit.
Heiko
Yes, GetStdHandle() would only need to be called once unless the handle
were to change during execution (fork_to_background()?).
I haven't done any exhaustive profiling but the attached patch doesn't
seem to affect performance. It calls determine_screen_width() every time
the progress bar is updated (~5 times per second?).
Note: I'm not suggesting we use the patch as-is, it's just a test.
It might be possible to implement something similar to SIGWINCH using
WinEvents, but that's not really what they were designed for. They were
designed to be used by accessibility software (screen readers, etc.),
and it may not be available on older versions of Windows.
How often do people change the size of the screen buffer while a command
is running?
Index: progress.c
===
RCS file: /pack/anoncvs/wget/src/progress.c,v
retrieving revision 1.43
diff -u -r1.43 progress.c
--- progress.c 2004/01/28 01:02:26 1.43
+++ progress.c 2004/01/28 19:37:50
@@ -579,6 +579,22 @@
/* Don't update more often than five times per second. */
return;
+#ifdef WINDOWS
+{
+ int old_width = screen_width;
+ screen_width = determine_screen_width ();
+ if (!screen_width)
+ screen_width = DEFAULT_SCREEN_WIDTH;
+ else if (screen_width MINIMUM_SCREEN_WIDTH)
+ screen_width = MINIMUM_SCREEN_WIDTH;
+ if (screen_width != old_width)
+ {
+ bp-width = screen_width - 1;
+ bp-buffer = xrealloc (bp-buffer, bp-width + 1);
+ }
+}
+#endif
+
create_image (bp, dltime);
display_image (bp-buffer);
bp-last_screen_update = dltime;
VIRUS IN YOUR MAIL
V I R U S A L E R T Our viruschecker found the W32/[EMAIL PROTECTED] virus in your email to the following recipient: - [EMAIL PROTECTED] Delivery of the email was stopped! Please check your system for viruses, or ask your system administrator to do so. For your reference, here are the SMTP envelope originator and headers from your email: From [EMAIL PROTECTED] - BEGIN HEADERS - Return-Path: [EMAIL PROTECTED] Received: from sunsite.dk (ppp-166-131.aijv.com.au [202.61.166.131]) by mail1.rsvp.com.au (8.12.5/8.12.5) with ESMTP id i0R79GiA017479 for [EMAIL PROTECTED]; Tue, 27 Jan 2004 18:09:29 +1100 From: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Hi Date: Mon, 27 Jan 2003 14:36:24 +0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0003_19F99DBB.C6ADB1FA X-Priority: 3 X-MSMail-Priority: Normal -- END HEADERS --
VIRUS IN YOUR MAIL
V I R U S A L E R T Our viruschecker found the W32/[EMAIL PROTECTED] virus in your email to the following recipient: - [EMAIL PROTECTED] Delivery of the email was stopped! Please check your system for viruses, or ask your system administrator to do so. For your reference, here are the SMTP envelope originator and headers from your email: From [EMAIL PROTECTED] - BEGIN HEADERS - Return-Path: [EMAIL PROTECTED] Received: from sunsite.dk (ppp-166-131.aijv.com.au [202.61.166.131]) by mail2.rsvp.com.au (8.12.5/8.12.5) with ESMTP id i0R7CpUM009143 for [EMAIL PROTECTED]; Tue, 27 Jan 2004 18:12:51 +1100 From: [EMAIL PROTECTED] Message-Id: [EMAIL PROTECTED] To: [EMAIL PROTECTED] Subject: Server Report Date: Mon, 27 Jan 2003 14:38:31 +0800 MIME-Version: 1.0 Content-Type: multipart/mixed; boundary==_NextPart_000_0008_517DEEB9.A61B1D86 X-Priority: 3 X-MSMail-Priority: Normal -- END HEADERS --
Re: recursive and form posts in wget 1.9.1
On Tuesday 27 January 2004 05:23 pm, Hrvoje Niksic wrote: Greg Underwood [EMAIL PROTECTED] writes: I took a peek at my cookies while logging into the site in a regular browser. It definitely adds a session cookie when I log in, I think your problem should be solvable with `--keep-session-cookies'. The server will have no way of knowing that the two sessions are in fact different. For example: # Browse to the log in page to get a permanent cookie and the unique # string. (We keep session cookies just in case they get added too.) wget --keep-session-cookies --save-cookies login.txt LOGIN-PAGE-URL I tried that, and the logins.txt file was still empty. Can you give me an example of a URL that uses sessions cookies so I can see what is supposed to be written into the login.txt file when I do this first step? -Greg
hallo
I am using wget to try and retrieve multiple source files from the web. They are all located one site etc.. However, I am running into a rather interesting problem. In using wget -r -np -X blah/ http://blah.com I cant seem to get blah/ exclude from the pulled material. I have tried --exclude blah/, and I have also tried setting the exclude_directories variable in wgetrc. I have tried -X *blah/,*blah/*,*/blah,*/blah*,*blah* and just for giggles tried -X *. I am guessing the -r flag has to do with my problems. I have also tried -I in conjunction with -X with the same result. Anyone have ideas on what the problem is? I am using 1.9 under slack9.1 fyi. Thanks in advance! -klug p.s. I am not subscribed to this list so please include the replies in a cc to [EMAIL PROTECTED] thanks!
