Home > Application Error > Application Error #2800 Mantisbt

Application Error #2800 Mantisbt

Please see http://www.php.net/manual/en/session.configuration.php#ini.session.gc-maxlifetime ~0024880 javatopia (reporter) 2010-03-23 12:07 This is happening in 1.2. MantisBT itself has something like a 3 day expiry for form security tokens (the idea being that you may leave screens open on Friday and return on Monday to finish up We would like to put the change back, due to the security risk. If it is really necessary for some purpose (apart of training the people not to be relaxed), the behavior should be changed so as to preserve user input and allow the check my blog

How rich can one single time travelling person actually become? Why this bug fix does not added to 1.1.4 distrib? ~0019957 cstamas (reporter) 2008-11-20 16:00 In note 0019750 you say that $g_allow_browser_cache shall not be set, however it is used in Invalid form security token. 1. Question: why is this "feature" there and is there a way to either disable it or make it (a lot) longer timeout? https://www.mantisbt.org/bugs/view.php?id=12381

I'm in View Issues 2. How do I align the view to the local axis of an object? I hope now will be quite difficult to lose the form data. (0033622) ibs (developer) 2014-10-23 12:21 aiv, it works great! :) Notes Issue History Date Modified Username Field Change

  1. I'll tell ones who gets the problem to clean their browsers data, but I cannot control that unfortunately. ~0019755 skay (reporter) 2008-11-01 18:01 We are behind a proxy. ~0019761 secteur13 (reporter)
  2. For all forms that are protected by "form security token" (report page, add bug note etc.) a little bit of javascript code was added to handle the following: * when submitting
  3. Second direction is to prevent user from losing form data (if session has expired, or user tries to send form from page which was taken from browser cache or any other
  4. go Report issue 2.
  5. ibs, Good question, I'll think in this direction.
  6. But some of my clients and some of my co-workers can :/ Seems that we cannot reproduce the issue under Linux or MacOS (with Firefox), but under windows it has been
  7. Unfortunately, there is no way, that I know of, to "fix" Mantis to work in this situation, because it is your proxy server that is serving cached versions of pages from
  8. Recommendation is to 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).
  9. This could be caused by a session timeout, or accidentally submitting the form twice.
  10. function string_get_bug_page( $p_action, $p_user_id=null ) { if ( null === $p_user_id ) { if ( auth_is_user_authenticated() ) { $p_user_id = auth_get_current_user_id(); } } $g_show_action = config_get( 'show_' . $p_action ); $t_string

This is because we can potentially get performance problems if we don't limit this timeout. Unfortunately, this problem cannot be fixed without a major rework of the way sessions and form security are handled in MantisBT. The issue occurs on Firefox and IE the latest versions. The second bug-report after clearing the cache won't be accepted.

This could be caused by a session timeout, or accidentally submitting the form twice., then most likely the issue is caused by a PHP session timeout. It seems to me the problem of Application #2008 in Report Issue is due to the following line in bug_report_page.php $g_allow_browser_cache = 1; By commenting it out, Report Issue works fine I try the way of dplinnane but no effect. ~0019969 dirkdatzert (reporter) 2008-11-21 05:19 This error is not resolved. http://www.mantisbt.org/forums/viewtopic.php?f=2&t=19578 It seems it was a problem on our side. ~0021340 skay (reporter) 2009-03-31 09:09 @jreese: I have checked the "error 11" behaviour again.

mt_rand() ); } switch ( $g_show_action ) { case BOTH: if ( ( null !== $p_user_id ) && ( ON == user_pref_get_pref( $p_user_id, 'advanced_' . $p_action ) ) ) { return When I manually force the page to reload (either 'reload' button or F5), then I get the expected logging output. You can also click an option from the menu bar to go directly to a new section. ----- This is very annoying since in many cases it leads to all the I get "APPLICATION ERROR #2800".

As a note, in other PHP applications, I noticed that sometimes after using my session, the session just dies without any apparent cause. https://www.mantisbt.org/bugs/view.php?id=10293 I want to add that it is known MantisBT issue, and there no complex solution at the moment: http://www.mantisbt.org/docs/master-1.2.x/en/administration_guide.html#ADMIN.TROUBLESHOOTING.ERRORS.2800 [^] Error 2800 - Invalid form security token This error may only Seems also that the issue should happen when, for example, switching from a project to another. Hope it helps. ~0019852 AliG (reporter) 2008-11-12 10:34 I am running on Mantis 1.1.4, and I can reproduce all the time.

Join them; it only takes a minute: Sign up mantis bug reporting timeout up vote 2 down vote favorite When I report a bug in our Mantis system I sometimes take click site Get APPLICATION ERROR #2800. So when you try to add a note it throws back an error saying your security token was invalid, which is just a fancy way of saying your login timed out. Because niw we have to made the trade-off between security ( which was not present in older versions ) and usability for the users.

Does not seem to matter which browser we use - firefox or IE (all recent versions). Did you submit the form twice by accident? What do you think about this? (0027581) ibs (developer) 2014-01-21 18:06 aiv, great features! :) I have a question: could this javascript store user's information, refresh page, insert stored information in news This is a full reload of the page (see 0009698). ~0020831 augur (reporter) 2009-02-10 08:07 Hi.

Things are fine for the first reported issue, but I get the APPLICATION ERROR #2800, for the second one. Why did monero-wallet-cli restore the same wallet with different mnemonic seeds? While I don't have a lot of hackers going to my site - probably that could work for now. ~0029187 TomR (reporter) 2011-07-18 07:21 Last edited: 2011-07-18 07:27View 2 revisions I am

So the cache of the proxy should not cache the page, if the parameter changes every time and we can use the security validation.

Did you submit the form twice by accident? I think the delay between loading the form and submitting it is the key because it happened once in exactly the same way on my own tracker with 1.2.0a2 (trunk r5751). Which is faster? Once clean it, the bug did not appear any more. ~0019832 baltun (reporter) 2008-11-10 11:50 may be it will be usefull for developers and users: i've found that if you add

ps. It seems that upgrading to version 1.1.6 was a bad idea since Mantis is pretty much unusable right now. ~0021280 jreese (reporter) 2009-03-30 08:47 skay, check that you don't have any The fix has been committed to both the 1.2.x and 1.1.5 development trees. ~0019904 baltun (reporter) 2008-11-15 12:12 could you please give direct link to new distributive of 1.1.5 ? More about the author skay: I was unable to reproduce your error; I think it may be the result of an incorrect patching issue with 1.1.x, as I had to manually resolve conflicts when porting

Cheers Notes Related Changesets MantisBT: master 10040dee Timestamp: 2009-03-27 18:16:51 Author: jreese [Details] [Diff] Fix 0009999: allow form security to be disabled for sites that use 'bad' proxy servers. And there is no problem to add note when the page is just opened. Click "Report Issue" again. In one project I can't create a new bug entry.

If I rollback to version 1.1.1 everything works fine. ~0019754 JohanCwiklinski (reporter) 2008-11-01 05:55 Hi, Personnaly, I cannot reproduce the error. When requesting the bug submit page, a 302 not modified header is being sent back to the client which is why the same id is be passed back. ~0019765 secteur13 (reporter) Going back, copying the fields out, refreshing the form (clearing all the fields), pasting the fields in, and submitting worked. Bug is successfully submitted, which brings me back to View Issues 3.

This indicates that the browser is not reloading the page. Or (I guess the easiest way) just include this timeout in Java script which would disable button "Submit" on the report page after the timeout, and show the same message below I notice a lot of comments on the this bugtracker, the MantisBT forum and on the internet regarding this issue for quit some time, but do not find a solution. Edit: obviously a different problem, 0009814 submitted. ~0019868 ezraw (reporter) 2008-11-13 13:23 I've had a user report this as well, but none of our staff has ever had it occur, and

Chi-Yu, if you are not using a proxy, then you shouldn't be receiving these errors. It seems it's working now, but I can not order by diferent concepts in "View Issues" screen. Submit report 5. I was wondering it maybe a timeout setting for the page or Apache.

I have this in my php.ini file: session.gc_maxlifetime=14400 But that doesn't help. Same issue here. Still the same problem. We have updated a 1.1.1 installation to 1.1.6.