-
Notifications
You must be signed in to change notification settings - Fork 20
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Question: can the IIIF image server simply return files that are not images #82
Comments
If you use the CloudFront-enabled flavor, you can add additional origins and behaviors to the distribution it creates. I’ll have to give some thought to the best way to do that within the framework of a SAM deployment/CloudFormation stack, but you can play with the concept by making manual changes to the CloudFront distribution in the AWS console. |
We have all our images commingled on the same bucket with resources of all media types, and only in cases where our digital repository identifies the file as an images does it access it specifically through the IIIF server—everything else (videos, audio, pdf) is just accessed directly through the s3 endpoint with a presigned URL. Curious, is there a value you're trying to gain by also having non-images pass through the IIIF server or is it more a convenience thing? |
Thanks @mbklein! I'll do some tinkering...that is a good pointer. |
Thanks @fitnycdigitalinitiatives, It is more of a convenience thing at this point. |
I ended up creating a separate distribution for serving all files that aren't images. |
Hey guys;
If I wanted to have the IIIF server simply return files that aren't images (for example an mp4 file)...is there a recommended approach?
The text was updated successfully, but these errors were encountered: