Manifests not accessible

[jsbien]

I test the program, as suggested, on Google 1000 Books dataset. Viewing works OK, but the manifests are not accessible, e.g.
http://0.0.0.0:5000/iiif/Volume_0594/manifest.json
gives
The requested URL was not found on the server.

[jsbien]

This is an important bug for me as I would like to open the manifest in another viewer (either the embedded server or viewer seems rather slow and unstable on my computer). Moreover I'm just curious how it could happen, cf. https://iiif.slack.com/archives/C148SMLD7/p1555433727009600.

[nicolasfranck]

hard to debug: that manifest is only accessible on your local computer

[jsbien]

On Wed, Apr 17 2019 at 23:58 -07, Nicolas Franck wrote: hard to debug: that manifest is only accessible on your local computer

[...] Thanks for your comment. I hope you are overpessimistic. 1. Do I understand correctly that Mirador has no log facility? In my other experiments with different versions of Mirador it quite often just don't display the object described in the manifest with no error message. It is quite annoying but of course this is a Mirador issue. 2. What about adding some log facility to hocrviewer.py? What about writing to a file the copy of the manifest passed to Mirador? 3. As I said, I test the program on Google 1000 Books dataset. An obvious question is whether other userd can reproduce my problem. In particular, can you? Best regards Janusz

…

-- , Janusz S. Bien emeryt (emeritus) https://sites.google.com/view/jsbien

[jsbien]

The correct address of the manifest is http://0.0.0.0:5000/iiif/<id> while the incorrect link is http://0.0.0.0:5000/iiif/<id>/manifest.json