Revert "[BB-728] Add problem response report API" - #19903
Merged
ormsbee merged 1 commit intoFeb 28, 2019
Merged
Conversation
Contributor
Author
|
FYI: @fysheets, @giovannicimolin, @fredsmith, @feanil |
fysheets
approved these changes
Feb 28, 2019
Contributor
Author
|
jenkins run bokchoy |
|
Your PR has finished running tests. There were no failures. |
Contributor
|
EdX Release Notice: This PR has been deployed to the staging environment in preparation for a release to production on Friday, March 01, 2019. |
Contributor
|
EdX Release Notice: This PR has been deployed to the production environment. |
edx-secure
deleted the
revert-19635-giovanni/bb-728-add-problem-response-report-api-upstream
branch
March 10, 2019 15:13
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
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.
Reverts edx/edx-platform#19635
We suspect this is causing elevated CSRF Token related 403 errors in production on this endpoint, possibly because of the removal of
ensure_csrf_cookie. Reverting for now to unblock the release, with the expectation that we'll roll this back in with fixes once we have a better idea of what's going on.