-
Notifications
You must be signed in to change notification settings - Fork 15
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
Suggestions on CORS in Apache implementation notes #61
Comments
There is this currently: https://iiif.io/api/annex/notes/apache/ The cookbook group thinks this should be a guide rather than a recipe. |
@regisrob would you be interested in writing this guide for CORS that can go on the IIIF guides website? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since I recently faced the issue with different IIIF providers, I wonder if it would make sense to add a note in the Enabling CORS section to explain that the HTTP Header should also be present on the redirect response. When a manifest or info.json url is redirected to a new one, clients are still broken if the redirect is not itself cors-enabled.
I am not completely sure but I guess this can be solved in Apache by using
Header always set ...
.It might also be useful to point implementers to https://enable-cors.org, that has recipes for many servers other than Apache.
The text was updated successfully, but these errors were encountered: