Could not fetch the manifest
Hi Rainer,
This looks amazing. I tried to use several of our manifests, but they each give the ‘could not fetch manifest’ warning. I tried to understand the information that is provided additionally, but this is not my cup of tea, I’m afraid.
Do you think there is something wrong with the way we present our IIIF uri’s, I’m sure these two resource are not restricted.
https://access.iisg.amsterdam/universalviewer/#?manifest=https://hdl.handle.net/10622/ARCH00448.4?locatt=view:manifest
Log in to comment and vote
Comments3
Richard Zijdeman
Feb 5, 2025
oh doh! could I please erase this from the web? sorry, adding ‘just’ the manifest works great :)
Rainer Simon
Feb 6, 2025
The web forgets nothing ;-) I was just about to answer! But no worries - it’s a common mistake.
I’m actually trying to figure out how I can automatically identify whether the URL points to an HTML page rather than a manifest, and provide a better error message. (But in your case it’s tricky. Because the server actually does restrict the access to the viewer page via CORS, but not the manifest. From a server configuration perspective, this makes total sense. But in this case it also means liiive get’s kicked out as soon as it tries to fetch the URL.)
Richard Zijdeman
Feb 6, 2025
hi, i really don’t think that’s necessary. it was me not paying attention. if anything an example url in the ‘grey’ Paste IIIF URL text might help, but would also clutter the box.