X-Git-Url: http://git.vanrenterghem.biz/git.ikiwiki.info.git/blobdiff_plain/3aa705b38a03e4d0c936756e5a213604ba75829e..HEAD:/doc/bugs/cannot_login.mdwn diff --git a/doc/bugs/cannot_login.mdwn b/doc/bugs/cannot_login.mdwn index cd13ba313..d8a8d5a98 100644 --- a/doc/bugs/cannot_login.mdwn +++ b/doc/bugs/cannot_login.mdwn @@ -39,6 +39,8 @@ Thanks. --[[anarcat]] Update: now I can't login to the ikiwiki.info site anymore, getting the same errors as on the git-annex site. +Update2: it seems this is specific to the HTTP/HTTPS switch. If I use HTTPS, things work fine, but not with plain HTTP. So I'm moving this to the branchable wiki, as I am not having that problem on other ikiwiki sites. Maybe the bug specific to ikiwiki is the lack of clarity in figuring out wth is going on here... See + > This seems to be a concacentation of multiple unrelated problems with > different stuff, which is not a good bug report technique. Then to add to > the fun, you filed the same bug on branchable too. Sigh! @@ -58,3 +60,26 @@ the same errors as on the git-annex site. > to go back to a previous login form and try to reuse it. > > --[[Joey]] + +>> I am sorry. I thought the problem was originally related to ikiwiki +>> then figured it was *only* happening on branchable sites, so I figured +>> it was better to report it on the branchable.com forums. +>> +>> I know that there's a OpenID-specific issue, but I had such issues in +>> the past and succesfuly solved those. Because the timing of the emergence +>> of the problem, i felt there was a correlation between the two issues. +>> +>> 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]]