[Koha-bugs] [Bug 25032] Generic unhandled exception handling

[bugzilla-daemon at bugs.koha-community.org]

https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=25032

--- Comment #14 from Tomás Cohen Arazi <tomascohen at gmail.com> ---
(In reply to Jonathan Druart from comment #9)
> (In reply to Tomás Cohen Arazi from comment #4)
> > (In reply to Jonathan Druart from comment #3)
> > > I cannot test this, I get this scary message on /api/v1/app.pl
> > 
> > I don't know why are you pointing your API tool there or if it is related to
> > this or not. If you want to bypass the rewrite rules we have, the right path
> > to get to the API is:
> > 
> > GET /api/v1/app.pl/api/v1
> 
> You told me (pm) to try app.pl, what I did.
> With this patch it's still displaying the weird error, which does not appear
> without.

I'm not sure about that conversation as I haven't seen app.pl for years, but i
guess I might have miscommunicated.

> Apart of that, it does not work out of the box in koha-testing-docker
> because of permission issues on *existing* intranet-error.log:
> -rw-r--r-- 1 root root 0 Apr  3 08:05
> /var/log/koha/kohadev/intranet-error.log
> -rw-r--r-- 1 kohadev-koha kohadev-koha 0 Apr  3 08:05
> /var/log/koha/kohadev/opac-error.log
> 
> That make the init fails.
> 
> Once fixed, it works.

Yes, I'm not sure how to fix this in koha-testing-docker. Any ideas are
welcome. We could just 'touch' the files before starting the services.

> On question however, I think it makes sense to have the API calls logged
> outside of the usual Koha logs, but when there are called from outside Koha.
> Should we have them logged in a separate log file even when called from Koha?
> If you think so, should not we have 1 for OPAC, and 1 for staff?

I'm not sure how we could accomplish that. The API is only one, it is just that
some portions are designed to be used from the OPAC and others require
privileged access (staff operations). What we could do is adding the full
address that was used to access the route, that would give us hints on who
called it (even external systems)

-- 
You are receiving this mail because:
You are watching all bug changes.