-----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 dialog), which AFAIK can't be affected by CGI forms >>> or JavaScript, etc. >> I must admit that I don't understand how it works - only Sun knows, I >> guess. Fact is that it accepts basic auth when it's being pushed at it >> by wget. > > Very interesting. I like the idea of a web interface supporting > *both* HTTP and cookie-based authentication. There really should be a > way to force Wget to simply send basic authentication. Maybe we > should differentiate between --http-user and --http-password and the > username/password being sent directly in the URL? Whatever we do, it > might be impossible to both satisfy all use cases and avoid an > explicit option.
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. - -- Micah J. Cowan Programmer, musician, typesetting enthusiast, gamer... http://micah.cowan.name/ -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHrIwB7M8hyUobTrERAsqSAJ4/u/HwSJqvqqjKk5XDEP9IAFpJ1QCfQs4q oz2t6uvUeUvMIZqMJiAAzCg= =C2To -----END PGP SIGNATURE-----
