Hi, all!
Just implemented...
Request:
GET: /json/login?n=name&p=pass
Param names "n" and "p" are for compatibility with the current usage, and
may optionally be written out as "name" and "password".
or POST: /json/login
POST request body: { "payload":{"name":"...", "password":"..."} }
(POSTed login data doesn't land in the apache logs, so it's highly
preferred!)
Response:
{
"fossil":"ff6485c5c8a81716dc9d8a70e4eff3db623f5d54",
"timestamp":1316035948,
"payload":"BCB43F00AF73F290571512747DDFC8B3358C47836B4CFA56D9/CE59BB9F186226D8/stephan"
}
The response payload is the value of the fossil cookie, which also gets set:
Set-Cookie:fossil-CE59BB9F186226D8=BCB43F00AF73F290571512747DDFC8B3358C47836B4CFA56D9%2FCE59BB9F186226D8%2Fstephan;
Path=/cgi-bin/fossil.cgi; expires=Fri, 14 Sep 2012 04:32:28 GMT; HttpOnly;
Version=1
i might change the payload to also include the cookie name (fossil-CE5... in
the example above), but i don't yet know if i need it at this level.
i haven't yet done anonymous user support (that requires special handling
because of the random password). Nor have i yet thoroughly tested THIS
support (it's literally under 10 minutes old). "Seems to work."
--
----- 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
