Menu

CORS errors

2022-07-04
2022-09-09
  • Edu Hackenitz

    Edu Hackenitz - 2022-07-04

    We have in our IIPImage (version 1.1) a config setting FcgidInitialEnv CORS ""
    In the logs we see at startup: Setting Cross Origin Resource Sharing to '
    '

    I try to load images in the Mirador demo but it looks like it refuses due to absent CORS header
    Access to fetch at 'https://objects.library.uu.nl/fcgi-bin/iipsrv.fcgi?IIIF=/manifestation/viewer/61/34/46/61344645886288335197320146752907378847.jp2/full/400,400/0/default.jpg' from origin 'https://mirador-dev.netlify.app' has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource. If an opaque response serves your needs, set the request's mode to 'no-cors' to fetch the resource with CORS disabled.

    So that looks odd to me why the image is still refused

     
  • Ruven

    Ruven - 2022-09-09

    It's probably being blocked because Mirador uses javascript to request the images and for this you need to have a CORS header set, so you should try setting CORS to "" (or just https://mirador-dev.netlify.app if you only want to allow the Mirador demo to work with your images)

     

Anonymous
Anonymous

Add attachments
Cancel





MongoDB Logo MongoDB