New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[TT-657] Move CORS handler from chain to middleware to cover oauth2 endpoints #3462
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks solid!
/release to release-3 |
/release to release-3-lts |
/release to release-3.1 |
Working on it! Note that it can take a few minutes. |
@furkansenharputlu Succesfully merged |
Working on it! Note that it can take a few minutes. |
@furkansenharputlu Succesfully merged |
/release to release-3.1 |
Working on it! Note that it can take a few minutes. |
@furkansenharputlu Succesfully merged |
/release to release-3.2 |
Working on it! Note that it can take a few minutes. |
@furkansenharputlu Succesfully merged |
The reason for the move is that the oauth2 handlers don't have a chain in front of it but CORS is in the chain and it is the reason of why oauth endpoints don't support CORS. This PR moves it to routers middleware level to cover all endpoints in an API router.