On Wed, Sep 14, 2011 at 12:27 PM, Stephan Beal <[email protected]> wrote: > b) For non-login JSON requests, first check the request info (GET/POST) for > an authorization token. If found, i need to be able to tell fossil, "here's > your cookie - use this one." i.e. i need to be able to make fossil think it > got a cookie from the HTTP header, though i'm really feeding it the cookie > from JSON. > d) If no auth token is set in the request, check for it in the HTTP cookies > (i.e. do what fossil does currently).
Are you proposing supporting non-HTTP transport of JSON client-server interaction? If not, why would the auth token be put in the JSON payloead rather than in the HTTP headers? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
