master
https://www.google.com/accounts/o8/id?id=AItOawlcaGfdn9Kye1Gc8aGb67PDVQW4mKbQD7E 2011-03-20 20:19:06 +00:00 committed by Joey Hess
parent 70f6462488
commit efd9207e43
1 changed files with 12 additions and 0 deletions

View File

@ -121,3 +121,15 @@ the user agent to be programmatically manipulated? --[[schmonz]]
>> Pong.. I'd be happier with a more 100% solution that let cookies be used
>> w/o needing to write a custom plugin to do it. --[[Joey]]
>>> According to LWP::UserAgent, for the common case, a complete
>>> and valid configuration for `$config{cookies}` would be `{ file =>
>>> "$ENV{HOME}/.cookies.txt" }`. In the more common case of not needing
>>> to prime one's cookies, `cookie_jar` can be `undef` (that's the
>>> default). In my less common case, the cookies are generated by
>>> visiting a couple magic URLs, which would be trivial to turn into
>>> config options, except that these particular URLs rely on SPNEGO
>>> and so LWP::Authen::Negotiate has to be loaded. So I think adding
>>> `$config{cookies}` (and using it in the aggregate plugin) should
>>> be safe, might help people in typical cases, and won't prevent
>>> further enhancements for less typical cases. --[[schmonz]]