On Wed, Nov 23, 2011 at 12:07 AM, Stephan Beal <sgb...@googlemail.com>wrote:
> i forgot to mention that i have a horrible disease called, "can't sleep > when there's an easy bug which can be fixed." > And it gets worse as the night goes on :/. > So now the 64kb question is: if the cookie's _value_ is called > "authToken", what should the cookie's _name_ be called? i > The answer was staring my in the face: the C function is called login_cookie_name(), so: stephan@tiny ~/cvs/fossil/fossil $ f ci -m 'Added loginCookieName to /json/login response payload, mainly as a crutch for certain scripting cases (e.g. RSS feeds). Still TODO: add future expiry time of cookie/token to response.' src/json_login.c Autosync: http://step...@www.fossil-scm.org/fossil Bytes Cards Artifacts Deltas Sent: 177 2 0 0 Received: 1136 25 0 0 Total network traffic: 364 bytes sent, 784 bytes received New_Version: daa564c4df7894f2925179aa2521d21d5163258d i'll try to get the expiry time added tomorrow night, else it will have to wait until next week (there are two obvious solutions, neither of them very signed-32-bit-friendly, or it would already be implemented). @Jeremy: the lifetime of the login cookie is defined in the config table as "cookie-expire", in seconds (default=8766, though i have no idea where that unusual number originally came from). -- ----- 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
