Bug 37843 - No logs for any errors when trying to connect to remote SRU/z39.50 server
Summary: No logs for any errors when trying to connect to remote SRU/z39.50 server
Status: Needs Signoff
Alias: None
Product: Koha
Classification: Unclassified
Component: Z39.50 / SRU / OpenSearch Servers (show other bugs)
Version: unspecified
Hardware: All All
: P5 - low enhancement
Assignee: Peter Vashchuk
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-05 14:02 UTC by Peter Vashchuk
Modified: 2024-10-19 18:41 UTC (History)
3 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:
Circulation function:


Attachments
Bug 37843: Add warn to log errors when trying to connect to a remote SRU/z39.50 server (29.93 KB, patch)
2024-09-05 14:07 UTC, Peter Vashchuk
Details | Diff | Splinter Review

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Vashchuk 2024-09-05 14:02:18 UTC

    
Comment 1 Peter Vashchuk 2024-09-05 14:07:21 UTC
Created attachment 171075 [details] [review]
Bug 37843: Add warn to log errors when trying to connect to a remote SRU/z39.50 server

Before this patch, when attempting to connect
to a remote SRU/z39.50 server, errors such as
incorrect URLs (404 error) or forgetting https
(trying to access an https endpoint using http,
resulting in a 400 error) were silently ignored.
The system would simply return "nothing found"
without logging any errors, making it difficult
to troubleshoot connection issues. Also added
error codes explanation
(src: https://www.loc.gov/z3950/agency/contributions/1.html)
Comment 2 David Nind 2024-10-19 18:41:36 UTC
Could we get a test plan for this? 

Then I would be happy to test.

For example, how to replicate or demonstrate the issue (for the various errors), and then showing it is fixed or improved.