Skip to content

Incorrect request populated as context for mutation #56

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

Closed
maxlang opened this issue Nov 9, 2018 · 0 comments · Fixed by graphql-python/graphql-core-legacy#260
Closed

Comments

@maxlang
Copy link

maxlang commented Nov 9, 2018

I posted about this on stackoverflow, but figured I'd ask about it directly here as well: https://stackoverflow.com/questions/53233291/python-flask-and-graphene-incorrect-request-causes-security-issue

Basically, the issue is that when I try to perform a high volume of mutations as one user while another user is making requests as well, some number of those mutations are made as the wrong user.

The issue seems to go away when I run with gunicorn instead of FLASK_ENV=production flask run

I know the context is populated here: https://github.com/graphql-python/flask-graphql/blob/master/flask_graphql/graphqlview.py but the context for the query is incorrect in this case.

I was wondering if anyone had seen this issue before, or could point me in the right direction so I can figure out what's wrong.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant