summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorzsloan2024-06-03 17:43:21 -0500
committerGitHub2024-06-03 17:43:21 -0500
commit5c0597561611c91023f43fe6a08c13d995675b5e (patch)
treed486cac1b497789258edb9ce5e80653ab3e46ab4
parent99fb6ae36bf03fc06c84e4ae45e741c6f7c0902a (diff)
downloadgn-gemtext-5c0597561611c91023f43fe6a08c13d995675b5e.tar.gz
Create old_session_bug.gmi
-rw-r--r--issues/old_session_bug.gmi17
1 files changed, 17 insertions, 0 deletions
diff --git a/issues/old_session_bug.gmi b/issues/old_session_bug.gmi
new file mode 100644
index 0000000..649ea46
--- /dev/null
+++ b/issues/old_session_bug.gmi
@@ -0,0 +1,17 @@
+# Error when loading GN2 with old pre-update session
+
+## Tags
+
+* status: open
+* priority: medium
+* type: bug
+* assigned: zsloan, fredm
+* keywords: gn-auth, gn2
+
+## Description
+
+Something about the recent updates (and by "recent" it could be anything from the last 3-5 months) caused old "anonymous" sessions to cause an error if they were still active after updating production GN2.
+
+This issue can be fixed on the client's end by deleting cookies, but ideally there would be some way to prevent this.
+
+Probably not super high priority, but it would still be good if the website could deal with an issue like this without completely shutting down (ideally if something goes from with the session/cookie it would simply behave as if you weren't logged in).