James Wiebe <[EMAIL PROTECTED]> writes: > How do you get past an https login screen (as opposed to a plain > http (non-secure) one)?
The procedure is, as far as I know, exactly the same for both. > Using an idea from msg "Login string" Richard Emanilov Wed, 16 Mar 2005 > 13:38:09 -0800 > I tried > wget --http-post="[EMAIL PROTECTED]&password=mypswd" -R gz -nv > https://jdoe%40mydom.net:[EMAIL PROTECTED]/mailman/private/pgp-users/ > Result: > wget: unrecognized option [EMAIL PROTECTED]&password=mypswd' The option name is `--post-data'. The incorrect name probable comes from an entry in the Wget FAQ which has since been fixed. Also, the form in question uses the name "username", not "login". The best way to deal with it would probably be: $ wget --post-data "[EMAIL PROTECTED]&password=mypswd" \ --save-cookies=cookies.txt --keep-session-cookies This will authorize you on the server and save the generated cookie to "cookies.txt". For further downloads you can specify --load-cookies: $ wget --load-cookies=cookies.txt -r ... > -There was no --https-user and pswd setting, unfortunately. Am I > out of luck? https uses the same options for username and password, but the page is not using the HTTP authentication directly, it uses a login form and cookies.
