| 2005-09-07 16:30:58 |
Paul Sladen |
bug |
|
|
added bug |
| 2005-11-03 16:58:33 |
Brad Bollenbach |
malone: status |
New |
Accepted |
|
| 2005-11-03 16:58:33 |
Brad Bollenbach |
malone: assignee |
|
bradb |
|
| 2006-01-12 08:33:29 |
Matthew Paul Thomas |
malone: assignee |
bradb |
stevea |
|
| 2006-01-26 16:48:58 |
Steve Alexander |
launchpad: statusexplanation |
|
|
|
| 2007-01-05 04:42:00 |
Matthew Paul Thomas |
title |
POST request fails if user not authenicated (eg. launchpad restarted) |
POST request fails if user not authenticated (eg. launchpad restarted) |
|
| 2007-02-06 21:24:43 |
Matthew Paul Thomas |
launchpad: importance |
Medium |
Low |
|
| 2007-02-06 21:24:43 |
Matthew Paul Thomas |
launchpad: statusexplanation |
|
Not as important now, because it occurs only if you clear your cookies. But it's still a problem that (for example) Bugzilla has solved. |
|
| 2007-05-18 23:28:59 |
Joey Stanford |
launchpad: statusexplanation |
Not as important now, because it occurs only if you clear your cookies. But it's still a problem that (for example) Bugzilla has solved. |
|
|
| 2007-11-26 22:49:45 |
Francis J. Lacoste |
launchpad: assignee |
stevea |
|
|
| 2011-04-25 06:12:05 |
Robert Collins |
summary |
POST request fails if user not authenticated (eg. launchpad restarted) |
POST request fails if user not authenticated |
|
| 2011-04-25 06:12:29 |
Robert Collins |
description |
A page submit using a POST request fails with the message:
Application error. Unauthenticated user POSTing to page that requires authentication.
if the user is not logged in. This can happen when somebody has been editing a page/form and Launchpad has been restarted in the mean-time. This leads to data loss, particularly if the /previous/ page was call generated by a POST and marked uncachable (meaning it's not even possible to go backwards and copy+paste the data elsewhere).
In the above situation, the user should be directed to login to Launchpad and then save the data after this has happened.
|
A page submit using a POST request fails with the message:
Application error. Unauthenticated user POSTing to page that requires authentication.
if the user is not logged in. This can happen when somebody has been editing a page/form and Launchpad's session database has been purged in the mean-time. This leads to data loss, particularly if the /previous/ page was call generated by a POST and marked uncachable (meaning it's not even possible to go backwards and copy+paste the data elsewhere).
In the above situation, the user should be directed to login to Launchpad and then save the data after this has happened. |
|
| 2011-04-25 06:15:01 |
Robert Collins |
launchpad: status |
Triaged |
Won't Fix |
|
