Hi Ben, great video! I was following along and saw that my set-cookie wasn't set, but also kinda just realized that it 'started working' even after hard refreshing and rigorous testing for about an hour just to see what happened. I honest to god have no darn clue what happened but I am super grateful to you nonetheless!! I love your videos and they've been a real lifesaver!

@bawad

5 жыл бұрын

Glad you got it 👍

I've been stuck on a cookie problem the last couple of days and this video really helped me out. Thanks!

@eggrat3381

Жыл бұрын

hey can you help me out I am not able to work my session cookie out. ive been stuck for 3 days

I ran into the problem that cookie doesn't appear in browser and has been searching for a solution for two days now I tried everything and it doesn't work and then I find the solution at 10 seconds in this video 😂 Thank you man appreciate it ❤❤

Thanks Ben, though the video was uploaded 3 years go still helping many devs. Thanks a ton

When i am trying to set cookie i can see it in headers section but aint visible in application tab......i tried everything but can get around it!

@GautamMalik-ir3ep

5 ай бұрын

Hi did u find the solution to the problem I'm stuck with the same problem :(

@sanjusaju4049

5 ай бұрын

@@GautamMalik-ir3ep if using fetch or axios ...set this configuration to ur fetch credentials: 'include' For axios I'm assuming it's withCredentials :'include'

@GautamMalik-ir3ep

5 ай бұрын

It worked ! Thank you😊

@sanjusaju4049

5 ай бұрын

@@GautamMalik-ir3ep wlcm

Hi my problem is even if I am on localhost the cookies are being set but it is being removed after a refresh. My backend and frontend are both on localhost.

thank you so much ! This video just saved me from miserable pain

Thanks for the video Ben. I had this issue few months ago.

for some reason the cookie shows up in the mozilla header but the cookie does not show up on chrome nor mozilla. What does this mean?

How about the cookie was sent and appears on the network tab but it's being saved innthe application/coolies tab.

@hackak3271

Жыл бұрын

Same issue! Someone please help me with this!

Hi, how can i set the domain if i working with a localhost in the front? The backend is in another port of localhost too

i'm working with #Fastfiy and #Nextjs and the only thing that caused the cookie not being set on the browser (normally received in the response header) was the domain option you need to omit it entirely

Safari doesn't allow cross domain cookies, I managed to get the cookies work by changing safari settings, is there a way for this problem because It's so inconvenient to ask people to change their safari settings before browse the website. Thanks for the video.

wow...This is exactly the video i wanted

Thanks a lot!❤

thanks a lot u r great u solved my problem keep it up . thanks......

bro saved my time thanks a lot

@eggrat3381

Жыл бұрын

hey can you help me out

9:56 Ben, did you do that video?

how to know about trust proxy

Hey Ben! You dont hide the x-powered-by header. 😊 Btw I love your videos. I think your videos solves some real life issues with development. I also want to know how we can restrict one login at time on the web. Please help me or make a video on it. I really need this.

@bawad

5 жыл бұрын

Like you only want to allow an account to have 1 session at a time?

@numtostr

5 жыл бұрын

@@bawad Yes. Regardless of which browser on even incognito mode. Is it possible?

@bawad

5 жыл бұрын

Yeah give express-session a try and only let them have a single session

I am on the 13th hour of your latest tutorial. Everything deployed fine. Cookie is being set on login and then on refresh it disappears. I tried setting my custom domain in the cookie settings. Re-deployed my backend but no luck. So I watched this video, downloaded firefox to test it and can't reproduce the issue in Firefox! I can refresh in firefox and the cookie sticks around. It seems to work. Any idea why I can't get it working in chrome?

@johnmcneill1998

3 жыл бұрын

I just tried it in chrome on a different computer and it works fine. It just doesn't work on my dev computer. I tried a hard reload and cleared cache but nothing.

@bawad

3 жыл бұрын

if you've tried everything in this, then I have no idea

@kunalchandel8987

3 жыл бұрын

Hey I think you have enabled in your chrome settings "block all third party cookies in your browser" you can get rid of it by going to "Cookies and Other site Data" and allowing it, i think this will work, Thanks

@tiarnanswayne7786

3 жыл бұрын

Did you ever fix it? I have the same problem right now. Although cookie doesn't stick around in firefox either.

you are a god damn life saver

Nice video Ben, could you please consider making a series releated to IAM solutions such as FusionAuth fusionauth.io/articles/logins/types-of-logins-authentication-workflows or maybe www.keycloak.org/ ?

@bawad

5 жыл бұрын

when I learn about IAM sure

@ComisarioLobo

5 жыл бұрын

@@bawad I think you already know about Identify and Access Management since you write your own authentication and authorization server with JWT, refresh tokens and cookies. Although it might be nice to have that IAM component outsourced to an open source tool such as FusionAuth or Keycloak without relaying on payed services such as Auth0

@bawad

5 жыл бұрын

yeah when I try out on of those guys or maybe ory hydra I'll make a video on it

Hello ben, thank you for helping us! I know it's been a while since you made this video, but I can't get the set-cookie to save a token in the browser. I made the configuration as presented in this video and also in this here: kzread.info/dash/bejne/ZGl7tZKGfLeeerg.html, but I just do not know why the token is not saved in the browser. My backend configuration is this: pastebin.com/6s3CzmGH and here is my setting that I put the cookie in response: pastebin.com/1DYZpdqB and here's how I make the request for the backend: pastebin.com/gV4mgs8s thanks again for your work and when you can take a look, I will be very grateful!

So I’m getting the set-cookie response but it’s not actually setting the cookie while I’m doing local dev. Browser: Chrome & Edge & Firefox Front end is at localhost:3000 Back end is at localhost:4000/graphql Cors is weird and keeps defaulting to allow-origin: * even though I have set ‘localhost:3000’ as my origin. Apollo Client is also suggesting I use ‘same-origin’ instead of include for my credentials value. The annoying part is going to the GQLPlayground sets the cookies and works perfectly, just doing it through the front end is a nightmare. I’m almost ready to do localstorage JWT to get around this damn cookie issue but I want to make it work. Any suggestions?

@bawad

5 жыл бұрын

This is most likely related to cors I recommend turning off cors from apollo: apolloServer.applyMiddleware({ app, cors: false, }); And using cors middleware: app.use( cors({ credentials: true, origin: process.env.CLIENT_HOST }) ); I would start with credentials set to include and once you get that working, consider same-origin

@MJW2291

5 жыл бұрын

Ben Awad ... I had no idea Apollo server included a cors middleware. I have applying cors directly to express and I guess it’s been getting overwritten by the Apollo server one. I turned it off via applyMiddleware and now I’m all set. Thank you!