RE: Wget and Yahoo login?

2008-08-21 Thread Tony Lewis
Micah Cowan wrote:

 The easiest way to do what you want may be to log in using your browser,
 and then tell Wget to use the cookies from your browser, using

Given the frequency of the login and then download a file use case , it
should probably be documented on the wiki. (Perhaps it already is. :-)

Also, it would probably be helpful to have a shell script to automate this.

Tony



Re: Wget and Yahoo login?

2008-08-21 Thread Micah Cowan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

Tony Lewis wrote:
 Micah Cowan wrote:
 
 The easiest way to do what you want may be to log in using your browser,
 and then tell Wget to use the cookies from your browser, using
 
 Given the frequency of the login and then download a file use case , it
 should probably be documented on the wiki. (Perhaps it already is. :-)

Yeah, at
http://wget.addictivecode.org/FrequentlyAskedQuestions#password-protected

I think you missed the final sentence of my how-to:

 (I'm going to put this up on the Wgiki Faq now, at
 http://wget.addictivecode.org/FrequentlyAskedQuestions)

:)

(Back to you:)
 Also, it would probably be helpful to have a shell script to automate this.

I filed the following issue some time ago:
https://savannah.gnu.org/bugs/index.php?22561

The report is low on details; but I was envisioning something that would
spew out forms and their fields, accept values for fields in one form,
and invoke the appropriate Wget command to do the submission.

I don't know if it could be _completely_ automated, since it's not 100%
possible for the script to know which form fields are the ones it should
be filling out.

OTOH, there are some damn good heuristics that could be done: I imagine
that the right form (in the event of more than one) can usually be
guessed by seeing which one has a password-type input (assuming
there's also only one of those). If that form has only one text-type
input, then we've found the username field as well. Name-based
heuristics (with pass, user, uname, login, etc) could also help.

If someone wants to do this, that'd be terrific. Could probably reuse
the existing HTML parser code from Wget. Otherwise, it'd probably be a
while before I could get to it, since I've got higher priorities that
have been languishing.

Such a tool might also be an appropriate place to add FF3 sqllite
cookies support.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIrb0s7M8hyUobTrERAlVXAJ9YnAM7JiQrxrB/KclA1FXDnoVswgCdGO7t
Vaa98nhNRuEY4aLMx2BFXm0=
=ScoA
-END PGP SIGNATURE-


Upcoming Wget releases, issue reorganizations

2008-08-21 Thread Micah Cowan
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1

In Savannah, the name of the field value for Planned Release that was
previously 1.13 has just been renamed 1.14, and a new 1.13 target
has been added. I'll be moving some items currently targeted at 1.12 to
1.13, and some items that have just been moved to 1.14 will get moved to
the new 1.13 target.

If you have bookmarks to the 1.13 set of bugs in Savannah, that link now
goes to 1.14.

I've been very happy with the progress and improvements that have been
made to Wget over the last several months. My own productivity, though,
especially in the last couple of months, was somewhat less than I'd
hoped it would be. In particular, taking on co-maintainer
responsibilities with GNU Screen, and a brief hiatus to write GNU Teseq
(a program to aid in debugging Screen), ate up quite a bit of time. I
believe I'm close to stabilizing the balance between my work on Screen
and my work on Wget, but I'm behind where I wanted to be.

In the meantime, we've already got several really terrifically useful
features in the current tree, whose release I'd prefer not to hold back
longer than necessary. I may choose to punt some of the improvements I'd
been planning on Content-Disposition funkiness and such, and code
cleanup, and a bunch of small but not crucial fixes, and really anything
else that looks like it might prevent us from releasing near the turn of
the year.

Steven Schweda's copyright assignment is in for his nice batch of
changes for better VMS build-support and myriad FTP-related fixes; I
need to sift through a lot of that to see what we can pull in as-is and
what I want to adjust somewhat. I'm hoping to get as much of that in for
1.12 as possible - particularly the FTP adjustments, but may need to
punt some of it, even important bugfix pieces, until after the 1.12
release. If that's the case, though, I will ensure that
http://hg.addictivecode.org/wget/schweda/vms/ is kept up-to-date with
mainline, so that it will be essentially functional as a
1.12-plus-Schweda's-changes.

- --
Micah J. Cowan
Programmer, musician, typesetting enthusiast, gamer.
GNU Maintainer: wget, screen, teseq
http://micah.cowan.name/
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFIrfU07M8hyUobTrERAhG7AJ9bv2Q0vetKEcDhfPz2CEQEt+2b3gCeP207
0pu6CNB0sWrsbZqDaWZ7ddA=
=0ObC
-END PGP SIGNATURE-