Mantis Bug Tracker - Forums

I am trying to restrict the user management feature only to administrators.

When I include the following line in my config_inc.php file, and let the current session expiring,

$g_manage_user_threshold = ADMINISTRATOR;

I get a 414 error in all enviroments I have tested, which dissapear removing that line.

I do not know if it is a bug, or simply, this configuration option has some dependences with other configuration options which are not compatible.

federico wrote: 30 May 2019, 08:30 I get a 414 error

You mean HTTP 414 (URI Too Long ) error?

federico wrote: 30 May 2019, 08:30 $g_manage_user_threshold = ADMINISTRATOR;

Hard to believe that this changes anything, as this is the default setting in config_defaults_inc.php

Thank you, Atrol.

Yes, is that HTTP error. $g_manage_user_threshold is the last change I did before the error, so was the candidate. I test it in deep, and it is something related with my plugin, but I can not figure out what is going wrong. Seems as a circular reference somewhere. The ante-last action I did, was trying to let the menú option selected when page changes from sub menu.

atrol wrote: 30 May 2019, 16:32 You mean HTTP 414 (URI Too Long ) error?

Have you heard about this error before? Any ideas?

federico wrote: 02 Jun 2019, 08:15 Have you heard about this error before?

No

federico wrote: 02 Jun 2019, 08:15 Any ideas?

Check your webserver logs to find out the request with the long URI.
Check your webserver settings for the actual limit, e.g. for Apache http://httpd.apache.org/docs/2.2/mod/co ... equestline

Thank you, Atrol.

Unfortunately, I am working for a small organization with poor network resources, and your proposal would produces me to change configurarion in about 200 browsers manually.

I've found additional information. It happens when accessing the calendar plugin page, so my first candidate is a compatibility issue

Thank you again.

It was true. There was a compatibility issue with the calendar plugin due the mantisbt version was not the right one in one of the servers, but it not solve the main problem.

The problem was with a reauthenticate function call in a wrong place.