http://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=6803 Frère Sébastien Marie <semarie-koha@latrappe.fr> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |semarie-koha@latrappe.fr --- Comment #11 from Frère Sébastien Marie <semarie-koha@latrappe.fr> 2011-11-07 08:20:29 UTC --- (In reply to comment #10)
I still would like to have better test plan for this. Does this bug only happen when there is a connectivity issue with LOC?
You could modify the include in "MARC21slim2MODS3-1.xsl", in order to have the href point to a URI where the status in well-known (sorry not well explained... try with examples after...) In order to obtain check with a connectivity issue: - for test a DNS problem: change in "MARC21slim2MODS3-1.xsl", the href (line 3) with : "http://www.loc.gov.example.com/marcxml/xslt/MARC21slimUtils.xsl" This will result Koha trying resolving "www.loc.gov.example.com" (which should not exist), and see what happens. - for test a server error: (not exactly the same that before: DNS answered correctly, but no HTTP server found), replace by a valid DNS name where no HTTP server are running (for example "http://google-public-dns-a.google.com/marcxml/xslt/MARC21slimUtils.xsl", but you should prefer a local owned-host, instead of perform aggression to a public internet server) This will result Koha successfully resolv "google-public-dns-a.google.com", but cannot connecting to http service. - for test a 404 error: replace by "http://www.loc.gov/marcxml/xslt/MARC21slimUtils.xsl.noexistant". This will result Koha successfully resolv "www.loc.gov", successfully connect to http service, but (should) obtain a 404 error. -- Configure bugmail: http://bugs.koha-community.org/bugzilla3/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA Contact for the bug. You are watching all bug changes.