From f4b75b3b2cd913781e1c49d9fd5a376a27e71afd Mon Sep 17 00:00:00 2001 From: Joey Hess Date: Mon, 2 May 2016 09:33:59 -0400 Subject: [PATCH] response --- doc/bugs/cannot_login.mdwn | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/doc/bugs/cannot_login.mdwn b/doc/bugs/cannot_login.mdwn index 96d2bad4d..d8a8d5a98 100644 --- a/doc/bugs/cannot_login.mdwn +++ b/doc/bugs/cannot_login.mdwn @@ -72,3 +72,14 @@ Update2: it seems this is specific to the HTTP/HTTPS switch. If I use HTTPS, thi >> And indeed, there seems to be a HTTPS-related issue: both login mechanisms >> work fine when on HTTPS, and both fail on HTTP. So I don't see those things >> as being necessarily distinct. -- [[anarcat]] + +>>> I've explained how the "login failed, perhaps you need to turn on +>>> cookies?" can happen and what it means. Clearly nothing to do with +>>> http; clearly not specific to branchable. +>>> +>>> I just now logged into this site using openid over http, and it worked +>>> ok. I think it's more likely that the `time_bad_sig` problem occurs +>>> intermittently (which would make sense if it's a timing related issue), +>>> and so you've just so happened to see it when logging in with +>>> http and not https, than that there's actually a correlation. +>>> --[[Joey]] -- 2.39.2