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

Michalis Zisis <[email protected]> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |[email protected]

--- Comment #1 from Michalis Zisis <[email protected]> ---
Greetings,

i am facing the same issue in a similar case.

Likewise, the installation is connected to a restricted network, which is
routed through a proxy. In my case, the proxy settings are defined in
"/etc/environment". Moreover the library (due to being an old instance) has no
active plack service.

After upgrading from 23.11 to 24.05 the same issue occurs, with the api address
(https://servername/api/v1/) not responding to requests and returning a 404
error.

In "/var/log/koha/library/api-error.log" the same message appears "[ERROR]
Warning: Could not load REST API spec bundle: GET
http://json-schema.org/draft-04/schema: Connection refused at /usr/share
/perl5/JSON/Validator/Store.pm line 190."

To verify, I tried connecting the server through an other network that does
have any network restrictions, and koha functioned without an error.

So it seems that the api internally relies on retrieving the address
"http://json-schema.org/draft-04/schema"; and when this is not available, eg in
the case of using a restricted network/proxy, there is an internal error that
leads to generating a "404 not found" in the api.

In turn this causes errors in various sections, such as the patrons list
failing to load, due to api returning the 404 response.

In regards for a possible solution, i would propose the api to not fail to run
when it can't communicate in order to retrieve the needed (json) schema.
Possibly, there could be a check to the api call in case of network error that
would continue the api respose or some kind of fallback to a local storage of
the schema/standards, so that even in case the network is not accessible, the
api service would work.

Unfortunately, i do not have knowledge of the code the api service users in
order to suggest a specific fix.

Thank you

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are watching all bug changes.
_______________________________________________
Koha-bugs mailing list
[email protected]
https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs
website : http://www.koha-community.org/
git : http://git.koha-community.org/
bugs : http://bugs.koha-community.org/

Reply via email to