initial S3Proxy server configuration #953
Closed
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
Made it so that there is no CORS requests available, allowing only known headers, and require no authorization. There shouldn't be any other domains trying to access the resources in the S3 buckets since we'll me accessing it directly. If we want authorization then we need to make an AWS account which is responsible for this. Unknown headers should not be used since we'll be using already made API tools (AWS libraries/CLI) and they shouldn't act funny.
Made a mockup of S3Proxy in a JRE.
|
This branch is now antiquated for the N5-Exporter branch has up to data code which exacts the functionality this was meant to do. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
see #949