summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorhttp://mjr.towers.org.uk/ <http://mjr.towers.org.uk/@web>2008-11-06 09:27:47 -0500
committerJoey Hess <joey@kitenet.net>2008-11-06 09:27:47 -0500
commit81846ef42e61315082d23db281fef65ad6788001 (patch)
tree439a6c50134cd3f7d4ae30168f48543b3ad708dc /doc
parent256b3aeba8a1a9e41c2e89d9030a1a55be060540 (diff)
New bug report
Diffstat (limited to 'doc')
-rw-r--r--doc/bugs/login_page_should_note_cookie_requirement.mdwn5
1 files changed, 5 insertions, 0 deletions
diff --git a/doc/bugs/login_page_should_note_cookie_requirement.mdwn b/doc/bugs/login_page_should_note_cookie_requirement.mdwn
new file mode 100644
index 000000000..b87928da1
--- /dev/null
+++ b/doc/bugs/login_page_should_note_cookie_requirement.mdwn
@@ -0,0 +1,5 @@
+At the moment, you go through the login shuffle and then are told that cookies are needed, so you lose all your data and login again. It would be much slicker to note by the edit link, or at least on the login page, that cookies are required.
+
+Even better would be to only display the cookie note as a warning if the login page doesn't receive a session cookie.
+
+Best of all would be to use URL-based or hidden-field-based session tokens if cookies are not permitted.