This repository has been archived by the owner on Mar 10, 2020. It is now read-only.
Add authorization header config option #740
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
daviddias
suggested changes
Apr 23, 2018
There was a problem hiding this comment.
@lgierth any comments here?
Meanwhile, @prettymuchbryce, mind documenting this option and adding a test?
Nope I think this probably makes sense. One could use it e.g. to authenticate the pin endpoint. |
|
Closing in favor of #741 |
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.
One potential solution for #724, allowing for clients to optionally send an
Authorizationheader. This would allow an API gateway to authenticate each request before proxying it to an IPFS daemon.