From 68f4bc14c8dd2dc893065df9e4f6e310190d1940 Mon Sep 17 00:00:00 2001
From: Joey Hess <joeyh@joeyh.name>
Date: Fri, 20 Sep 2019 12:10:18 -0400
Subject: [PATCH] bug report

---
 ...https_login_leads_to_extremely_confusing_error.mdwn | 10 ++++++++++
 1 file changed, 10 insertions(+)
 create mode 100644 doc/bugs/http_login_after_https_login_leads_to_extremely_confusing_error.mdwn

diff --git a/doc/bugs/http_login_after_https_login_leads_to_extremely_confusing_error.mdwn b/doc/bugs/http_login_after_https_login_leads_to_extremely_confusing_error.mdwn
new file mode 100644
index 000000000..eae465f1d
--- /dev/null
+++ b/doc/bugs/http_login_after_https_login_leads_to_extremely_confusing_error.mdwn
@@ -0,0 +1,10 @@
+As reported by many confused users at 
+<http://git-annex.branchable.com/bugs/impossible_to_login_to_the_website_at_times/>
+a successful login can end up at the error message "Error: Login succeeded,
+but I don't remember why you were logging in [...]"
+
+This happens when the user has earlier logged into a site on its https
+url, but then later navigates to the http url, and is prompted to log in
+there.
+
+Workaround: Set `redirect_to_https`.
-- 
2.39.5