Re: wget and sunsolve.sun.com
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. In the meantime I found out that it seems to look at the User-Agent header as well - it behaves differently with Wget/1.10.2 and Wget/1.11. As they don't document anything, and provide no official interface for patch downloads, one can only guess what's going on. Anyway, I'm now using a crude hack which actually makes the combination of wget v1.11 and sunsolve work, see: http://www.par.univie.ac.at/solaris/pca/news.html#20080208 Even so, simulating form posts with Wget is possible, with --post-data or --post-file. It's not as complete as it should be, but it is technically capable of doing almost everything. Thanks - I might take that route in the future. Right now I feel I have wasted enough time with Sun's stupidity. You can ignore my request for a change in wget's behaviour. Looks as if it does everything right, and it's really only sunsolve's fault. Thanks for listening, Martin. -- Martin Paul | Systems Administrator Institute of Scientific Computing | [EMAIL PROTECTED] Nordbergstrasse 15/C/3, A-1090 Wien | Tel: 01 4277 39403 http://www.par.univie.ac.at/ | Fax: 01 4277 9394
Re: wget and sunsolve.sun.com
-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, although, now that I think about it, we _could_ have used --header to take care of this. Dunno why that didn't occur to me to suggest this before now. Though, of course, that's hardly a user-friendly option. - -- 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 iD8DBQFHrIzr7M8hyUobTrERAsFzAJ44l+4iCidhBFzi7mgWN+E4z+708gCaAgYG aQEYBLhpLWL6kWkLFUaSGLw= =HDgz -END PGP SIGNATURE-
Re: wget and sunsolve.sun.com
-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-
Re: wget and sunsolve.sun.com
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.
