Enable CORS and API access in configuration#805
Open
jscottelblein wants to merge 1 commit into
Open
Conversation
Uncomment CORS configuration for API access and WallaBagger extension.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Uncomment CORS configuration for API access and WallaBagger extension.
Description
Added API/OAuth location block (commented out by default)
Benefits of this PR and context
Browser extensions (i.e. WallaBagger) and other things requiring access need this.
How Has This Been Tested?
Using live on my own machines. If using something like Authelia/Authentik/TinyAuth be sure to also bypass the API/OAuth paths for the WallaBag container;
i.e.