Searched hist:ecad51dd492a107c65ae1265bcca591769433e6c (Results 1 – 3 of 3) sorted by relevance
| /dokuwiki/inc/Action/ |
| H A D | Denied.php | ecad51dd492a107c65ae1265bcca591769433e6c Fri Dec 17 21:32:51 UTC 2021 Andreas Gohr <andi@splitbrain.org> fix handling of loading auth backend
When a non existing auth backend was configured, the action router ran
into an infinie loop exception. The reason was that the denied action
required a configured auth system, but denying access should always
work.
Interestingly the problem did not occur when the auth backend signalled
a failure to load. This was because the auth backend was not properly
deinitialized. This is now done.
To aid debugging similar problems, fatal errors are now logged through
the logging mechanism in the action router
|
| /dokuwiki/inc/ |
| H A D | ActionRouter.php | ecad51dd492a107c65ae1265bcca591769433e6c Fri Dec 17 21:32:51 UTC 2021 Andreas Gohr <andi@splitbrain.org> fix handling of loading auth backend
When a non existing auth backend was configured, the action router ran
into an infinie loop exception. The reason was that the denied action
required a configured auth system, but denying access should always
work.
Interestingly the problem did not occur when the auth backend signalled
a failure to load. This was because the auth backend was not properly
deinitialized. This is now done.
To aid debugging similar problems, fatal errors are now logged through
the logging mechanism in the action router
|
| H A D | auth.php | ecad51dd492a107c65ae1265bcca591769433e6c Fri Dec 17 21:32:51 UTC 2021 Andreas Gohr <andi@splitbrain.org> fix handling of loading auth backend
When a non existing auth backend was configured, the action router ran
into an infinie loop exception. The reason was that the denied action
required a configured auth system, but denying access should always
work.
Interestingly the problem did not occur when the auth backend signalled
a failure to load. This was because the auth backend was not properly
deinitialized. This is now done.
To aid debugging similar problems, fatal errors are now logged through
the logging mechanism in the action router
|