View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0013246||mantisbt||authentication||public||2011-08-18 08:48||2017-09-10 06:33|
|Status||closed||Resolution||no change required|
|Summary||0013246: APPLICATION ERROR #2800 when submitting notes|
I have seen similar reports but I think none of them where covering exactly my problem. Whenenver I (or someone else, for that matter) tries to submit a note to an issue, they receive APPLICATION ERROR #2800 in most cases. It took me quite some time to write the note for the first time, maybe 15 minutes, and after I retyped it in maybe 1-2 minutes the second time, I got the error again. That time, I copied the text and pasted it again right after the error appeared, so in that case I could manage to submit the note.
My main concern here is that, when using the "back" button in the browser, the form field is cleared, so if someone has written a somewhat lengthy note, they will have to re-type everything if they are not aware of the problem and use copypaste to circumvent it. The error message says that one should go back and fix all mistakes, but that is impossible when the form field is cleared.
php: Using memcached sessions, session.gc_maxlifetime = 1440
|Tags||No tags attached.|
I'd also like to add that the problem didn't seem to appear in previous versions, or at least not as frequently.
My collegue who uses IE9 reports the same problem.
Regarding the error 2800, the problem is most likely caused by php session settings.
As the bug view page tends to remain open for a while before user eventually decides to type a note, by the time they click submit the session has expired. If the garbage collector has removed the session data, then the http form's security token (CSRF protection) is no longer valid.
You should increase session.gc_maxlifetime as appropriate (in the office I have it set to 8 hrs, so it's valid for a normal work day).
The issue with form data getting lost when hitting the back button is a different topic altogether (see 0012492 and others) for which there is currently no solution.
As indicated above, the session lifetime is set to 24 minutes here, I've had the problem with bug report pages that were open for a shorter time, though. There is so much other software out there which doesn't have this problem, by either logging the user in again, or by displaying the submission form again, but with the previous data being filled in again. I hope the latter can be implemented into Mantis at some point to make the whole bug entering process less tedious and annoying.
I agree with you that this is a serious issue that needs fixing.
It is being tracked in 0012492 and other related issues, and I'm sure will be resolved at some point.