On Tue, Nov 22, 2011 at 9:32 PM, Jeremy Cowgar <jer...@cowgar.com> wrote:
> 1. Use allow authuser=johndoe&authpass=**secret as a URL parameter > 2. Forget accessing secured RSS feeds > > Any other ideas? > > In theory (though i have not tested it), you can pass the login cookie as a GET parameter, as fossil internally treats GET/POST/COOKIE data identically for most purposes. The trick, then, is getting the login cookie. It has a project-specific name and is normally sent as a cookie. Its value (but not its name) can alternately be fetched via the JSON API, but that wouldn't help very much for this particular use case. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
