On Wed, Sep 14, 2011 at 7:24 PM, Stephan Beal <[email protected]> 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. -- ----- stephan beal http://wanderinghorse.net/home/stephan/
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
