On Monday 22 September 2003 01:45, you wrote:
> Mark Veltzer <[EMAIL PROTECTED]> writes:
> > On Monday 22 September 2003 00:20, you wrote:
> >> Sorry about the lack of response. Your feature requests are quite
> >> reasonable, but I have no idea of the timeframe when I'll work on
> >> them (they're not a priority for me). Perhaps someone else is
> >> interested in helping implement them.
> >>
> >> The things I planned to tackle for a post-1.9 release are
> >> compression support and proper password "manager".
> >>
> >> BTW, have you tried `--http-user' and `--http-passwd'? They're
> >> supposed to do pretty much what you describe.
> >
> > That's weied. I tried --http-user and --http-passwd and all is
> > working well. According to the documentation the following are
> > equivalent:
> >
> > wget -r --http-user=foo --http-passwd=bar http://my.org
> >
> > and
> >
> > wget -r http://foo:[EMAIL PROTECTED]
> >
> > But they are not. Version 1 works while version 2 doesnt ?!?
>
> Does the manual really say that they are equivalent?
>
> When you specify `--http-user' and `--http-passwd', they are used for
> *all* the downloads. When you specify the username and password in a
> URL, they are used for that URL and not others. That can be
> considered a bug, but that's how it is.
Hello!
This is from the wget manual page:
--http-user=user
--http-passwd=password
Specify the username user and password password on an HTTP server.
According to the type of the challenge, Wget will encode them using
either the "basic" (insecure) or the "digest" authentication
scheme.
Another way to specify username and password is in the URL itself.
Either method reveals your password to anyone who bothers to run
"ps". To prevent the passwords from being seen, store them in
.wgetrc or .netrc, and make sure to protect those files from other
users with "chmod". If the passwords are really important, do not
leave them lying in those files either---edit the files and delete
them after Wget has started the download.
This does not discuss these differences which implies that they are the same
and I think it should. A paragraph like this will do the trick:
When using --http-user and --http-passwd ALL resources downloaded
will use authentication which is not the case when specifying the
user and password in the URL to be downloaded in which case only
the URL will use authentication and any subsequent URL will use
no authentication.
In addition I would add a flag that makes the URL method work like the
explicit method and vice versa. This would cover all bases.
Cheers,
Mark
--
Name: Mark Veltzer
Title: Research and Development, Meta Ltd.
Address: Habikaa 17/3, Kiriat-Sharet, city.holon, Gush-Dan, country.israel
58495
Phone: +972-03-5581310
Fax: +972-03-5581310
Email: mailto:[EMAIL PROTECTED]
Homepage: http://www.veltzer.org
OpenSource: CPAN, user: VELTZER, mailto:[EMAIL PROTECTED], url:
http://search.cpan.org/author/VELTZER/
Public key: http://www.veltzer.org/ascx/public_key.asc, wwwkeys.pgp.net,
0xC71E5D38
