daisy encryption check should handle error conditions
Bug #595367 reported by
Anand Chitipothu
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Open Library |
New
|
High
|
Edward Betts | ||
Bug Description
I noticed in the error logs that daisy encryption check fails when the www.archive.org gives "111 connection refused" error. It is happening at about 100 times in a day.
The daisy encryption check should be robust enough to handle such error cases. It can retry for couple of times or assume that the book is not encrypted in case of error. It should not raise internal error in any case.
One such error:
http://
| description: | updated |
| Changed in openlibrary: | |
| assignee: | nobody → Edward Betts (edwardbetts) |
| importance: | Undecided → High |
| milestone: | none → general-bucket |
Revision history for this message
| Edward Betts (edwardbetts) wrote | #1 |
Revision history for this message
| Edward Betts (edwardbetts) wrote | #2 |
To post a comment you must log in.
archive.org is case sensitive, http://
http://
I could add a work-around to show-marc that detects bad case and redirects.