Michael B. Klein

Thanks for bringing this issue to my attention. I'll take a look at it and see if I can come up with a solution. It might be as easy as...

What URL are you requesting? - If it's `/iiif/2`, try an actual image request. The former `OK` response to the root resource broke when I switched from API Gateway to...

Splitting into issues #74 and #75 and closing.

I've reopened this issue as a bug and renamed it to reflect what's actually going on. This is similar to (but not exactly the same as) #52, and I believe...

In `node-iiif`, I was trying not to dictate the path prefix, even though `serverless-iiif` always uses `/iiif/2/`. The fix (which is almost done) involves `node-iiif` using a _default_ path prefix...

The PR is in. As soon as samvera-labs/node-iiif#23 is reviewed and approved for merging, I'll be able to release v4.0.2 with the fix.

1. `.tif` is going to remain the default for the moment, but I've created #76 that should give you the flexibility you need without changing code. 2. CORS handling was...

The cache bucket was never supposed to be publicly accessible. If it is, that's a bug. It should only be accessible by the CloudFront Origin Access Identity by [policy](https://github.com/samvera-labs/serverless-iiif/blob/main/sam/cloudfront/template.yml#L164-L178).

Please see [this comment](https://github.com/samvera-labs/serverless-iiif/issues/77#issuecomment-1185988653) for a discussion of the `@id` hostname issue. I had run into this before, but forgot what the real issue is (because we use a custom...

> Thanks @mbklein. > > Question: would it be problematic to turn off public access to the cache bucket? I know I can override the template myself, just wondering if...