diff options
| author | Joey Hess <joey@kitenet.net> | 2011-03-21 13:47:12 -0400 |
|---|---|---|
| committer | Joey Hess <joey@kitenet.net> | 2011-03-21 13:47:12 -0400 |
| commit | 14b8abe60f02a9a31eb4b7ad489e6806637610f7 (patch) | |
| tree | a260f52b60d453c2bc244e5e126522c2dc9e5628 /doc/plugins | |
| parent | e96ecf2f9317b0f7d547e86bcaf67b3aebecd8ea (diff) | |
| parent | 7be18bf29a26a40a9c401fb4f5ce8c2ef3e33ffb (diff) | |
Merge branch 'master' of ssh://git.ikiwiki.info/srv/git/ikiwiki.info
Diffstat (limited to 'doc/plugins')
| -rw-r--r-- | doc/plugins/aggregate/discussion.mdwn | 12 |
1 files changed, 12 insertions, 0 deletions
diff --git a/doc/plugins/aggregate/discussion.mdwn b/doc/plugins/aggregate/discussion.mdwn index a3336ee08..80788fb1b 100644 --- a/doc/plugins/aggregate/discussion.mdwn +++ b/doc/plugins/aggregate/discussion.mdwn @@ -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]] |