Use same CORS policy for /@:username and /users/:username#9485
Merged
Gargron merged 1 commit intomastodon:masterfrom Dec 10, 2018
Merged
Use same CORS policy for /@:username and /users/:username#9485Gargron merged 1 commit intomastodon:masterfrom
Gargron merged 1 commit intomastodon:masterfrom
Conversation
Fixes mastodon#8189 rack-cors being called before the application router, it does not follow the redirection, and we need a separate rule for /users/:username.
ykzts
approved these changes
Dec 10, 2018
hiyuki2578
pushed a commit
to ProjectMyosotis/mastodon
that referenced
this pull request
Oct 2, 2019
) Fixes mastodon#8189 rack-cors being called before the application router, it does not follow the redirection, and we need a separate rule for /users/:username.
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
3 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.
Fixes #8189
rack-cors being called before the application router, it does not follow
the redirection, and we need a separate rule for /users/:username.