On 14 Sep 2011, at 18:26, Stephan Beal wrote: > On Wed, Sep 14, 2011 at 7:24 PM, Stephan Beal <sgb...@googlemail.com> wrote: >> No, but for supporting clients which don't have cookies support. e.g. i've >> written Java HTTP client apps (using a similar API to this one, actually) >> but the client code doesn't support cookies, so it has to pass around its >> authentication in the JSON request. Cookies are, for purposes of the JSON >> API, the fallback and not the default. >> > BTW: many SOAP interfaces do this as well. When logging in you get a token > (which fossil stores as a cookie), and that token has to be included in > requests which require non-guest access.
HTTP basic authentication is widely supported in HTTP client libraries, and much less hassle to use than passing tokens around. Ben -- http://bens.me.uk/ _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
