-
Notifications
You must be signed in to change notification settings - Fork 734
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
playground session based auth, not sending cookie in the request. #364
Comments
I confirm this one is still a problem with Playground |
I'd love if this issue could get priority attention, as it's affecting us in our development (we use Yoga). If there's anyone else that should be explicitly tagged, please do. |
@vincenzo You can always chip in and help with it :) |
@HuVik I'd love to, but I am new to all this and don't really know where to start to fix this one, sorry :) Maybe someone in my team could help. I'll ask. |
@HuVik @timsuchanek Any of you could give me a steer in the right direction, here? |
This issue pertains to the following package(s):
What OS and OS version are you experiencing the issue(s) on?
Chrome/Opera
What version of graphql-playground(-electron/-middleware) are you experiencing the issue(s) on?
1.3.6
What is the expected behavior?
Send cookie on the request.
What is the actual behavior?
Not sending the cookie in the request, unlike graphiQL.
What steps may we take to reproduce the behavior?
We're using passport-local as a middleware.
We use the mutation login and if it works we get back a cookie.
If I want to check who is the current user, I send my query and the cookie (passport) should be included in the request where the resolver should return either the current user or null in case the user has logout or if the cookie wasn't sent.
what graphiQL is sending:
What playground is sending:
The text was updated successfully, but these errors were encountered: