koha-bugs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Koha-bugs] [Bug 1337] New: 2.2.8 - Z3950 search error handling needs to


From: bugzilla-daemon
Subject: [Koha-bugs] [Bug 1337] New: 2.2.8 - Z3950 search error handling needs to be a little more robust
Date: Wed, 2 May 2007 11:39:00 +1200 (NZST)

http://bugs.koha.org/cgi-bin/bugzilla/show_bug.cgi?id=1337

           Summary: 2.2.8 - Z3950 search error handling needs to be a little
                    more robust
           Product: Koha
           Version: branch 2.2
          Platform: PC
               URL: http://article.gmane.org/gmane.comp.misc.koha/7339/
        OS/Version: All
            Status: NEW
          Severity: normal
          Priority: P2
         Component: z39.50 Server
        AssignedTo: address@hidden
        ReportedBy: address@hidden
         QAContact: address@hidden


I came across a number of situations in which the Z3950 search client does not
error out gracefully but returns a 500 Internal Server Error.  Original email
to the list is referenced in the URL.

1) Invalid login/password for Z3950 server when only that server is searched. 
Actually if all the servers return some type of error then you get an Internal
Server Error.

2) Using the npl templates (after fixing the "/" issue) and searching on more
than one keyword.
1 z3950.loc.gov error @attr 1=4  lord of the rings: Invalid query (10010)
0 amicus.collectionscanada.ca error @attr 1=4  lord of the rings: Invalid
query (10010)
[Wed Mar 28 21:49:47 2007] [error] [client 172.16.1.10] Premature end of
script headers: /var/www/koha/intranet/cgi-bin/z3950/search.pl

3) Searching library.dts.edu using Title/Author with possibly more than one
result returned??? I'm not sure exactly what it's returning but it works fine
when searching by isbn.  Configuration page is here
http://library.dts.edu/Pages/Help/Tech/z39.50.shtml




------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




reply via email to

[Prev in Thread] Current Thread [Next in Thread]