Micah Cowan wrote:
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, and needs some
means to get it back.
Hm, although, now that I think
Micah Cowan wrote:
Then, how was --http-user, --http-passwd working in the past? Those only
work with the underlying HTTP authentication protocol (the brower's
unattractive popup dialog), which AFAIK can't be affected by CGI forms
or JavaScript, etc.
I must admit that I don't understand how it
-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, and needs some
means to get it back.
Hm,
-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 authentication protocol (the brower's
unattractive popup
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 authentication protocol (the brower's
unattractive popup dialog), which AFAIK can't be affected by CGI forms
or JavaScript, etc.
I
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 was confident I could get rid
of Wget's insecure practice of doing so.
After some further
-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 was confident I could get
