You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all thanks for building Heurist but I have a small (configuration?) issue with the IIIF functionality. When uploading a media file to Heurist and making it public, the IIIF manifest is correctly created and usable in the internal mirador viewer. Perfect!
Problem Unfortunately there seems to be a configuration issue (at least on huma-num.fr): the IIIF resources are not viewable in an external viewer due to a configuration issue:
The expected behaviour is, of course, to be able to interact with the IIIF resources in other places as well. It seems that the resource permissions are set correctly when making them public.
Reproduce: to reproduce this issue, make a media file public on huma-num.fr and copy the IIIF manifest into an external IIIF viewer.
Potentially a solution would be to configure the web-server to return correctly configured Access-Control-Allow-Origin headers which allow to re-use IIIF resources and perhaps document this for other installs as well.
Thanks in advance.
The text was updated successfully, but these errors were encountered:
JorenSix
changed the title
CORS issue - No Access-Control-Allow-Origin header is present on the requested resource
CORS issue for public IIIF resources - No Access-Control-Allow-Origin header is present on the requested resource
Feb 28, 2024
First of all thanks for building Heurist but I have a small (configuration?) issue with the IIIF functionality. When uploading a media file to Heurist and making it public, the IIIF manifest is correctly created and usable in the internal mirador viewer. Perfect!
Problem Unfortunately there seems to be a configuration issue (at least on huma-num.fr): the IIIF resources are not viewable in an external viewer due to a configuration issue:
The expected behaviour is, of course, to be able to interact with the IIIF resources in other places as well. It seems that the resource permissions are set correctly when making them public.
Reproduce: to reproduce this issue, make a media file public on huma-num.fr and copy the IIIF manifest into an external IIIF viewer.
Potentially a solution would be to configure the web-server to return correctly configured
Access-Control-Allow-Origin
headers which allow to re-use IIIF resources and perhaps document this for other installs as well.Thanks in advance.
The text was updated successfully, but these errors were encountered: