Thanks for the help in reading the manual ;-) Also I didn't know or realize that you have to post to the name that the form requires -- your tip(s) was very enlightening.
Although I'm now having sufficient success in downloading, I still can't seem to recurse past certain levels of pages to get the .html files that have the actual content... Hold it! Now I'm getting them (it's running while I'm typing). I read in the manual that wget does "breadth" first; so it downloads all the subdirs in pgp-users/ with their author, subject, date and thread.html files first, and then goes back to download all the (eg) 020280.html files to which the former link (to). I had misunderstood the manual and thought that "breadth" meant doing "depth" first. It looks like everything is working. --- Hrvoje Niksic <[EMAIL PROTECTED]> wrote: > 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="login=jdoe%40mydom.net&password=mypswd" -R gz -nv > > https://jdoe%40mydom.net:[EMAIL PROTECTED]/mailman/private/pgp-users/ > > Result: > > wget: unrecognized option > > `--http-post=login=jdoe%40mydom.net&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 "username=jdoe%40mydom.net&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. > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
