This repository has been archived by the owner on May 12, 2023. It is now read-only.
adding additional CORS header for Curate integration #71
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
ialford
requested review from
jeremyf,
jonhartzler,
hanstra,
jgondron and
SteveMattison
jeremyf
suggested changes
May 6, 2019
| - Id: CSRFCorsHeader | ||
| AllowedHeaders: | ||
| - X-CSRF-Token | ||
| AllowedMethods: |
There was a problem hiding this comment.
Can we add HEAD and OPTIONS? Or are those implicitly a subset of GET?
There was a problem hiding this comment.
OPTIONS is not supported by S3 configurations - we can add HEAD without too much of a problem. See: AWS S3 CloudFormation Reference
jeremyf
approved these changes
May 6, 2019
jgondron
approved these changes
May 6, 2019
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For the CurateND Image Viewer integration, we discovered that the headers being sent by the application were not the
Authorizationheaders being used elsewhere, but rather wereX-CSRF-Token.This updates the Manifest bucket to allow these CORS headers so Curate can show the ImageViewer in an iFrame.