POST request fails if user not authenticated
Bug #2115 reported by
Paul Sladen
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Launchpad itself |
Won't Fix
|
Low
|
Unassigned |
Bug 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'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.
Changed in malone: | |
assignee: | nobody → bradb |
status: | New → Accepted |
Changed in malone: | |
assignee: | bradb → stevea |
Changed in launchpad: | |
assignee: | stevea → nobody |
To post a comment you must log in.
I've just lost a large post to 2117, because of the above bug! (Pressing back caused the page to be reloaded because of the [sodding] uncachability---and hence lose the post that wasn't able to be submitted).
This is a bug that I've experienced *enough times* in my first 24 hours of trying to use Malone that I'm wondering if I can really be bothered to waste time writing details if there is a 33% of losing them.
Yes, this is 10x more annoying that not being able to post a bug-report in the first place.