Cookies in Remix
HTML-код
- Опубликовано: 5 авг 2024
- A cookie is a small piece of information that your server sends someone in a HTTP response that their browser will send back on subsequent requests. In this Single we explore how to create, write, and read cookies to manage user authentication.
Explore the full code here 👉 github.com/remix-run/example-...
00:00 - Overview
00:39 - Scaffolding a createAccount function
03:20 - Creating a cookie
04:14 - Writing the cookie
05:30 - Cookie attributes explained
09:03 - Reading the cookie
11:22 - Review
Learn more at remix.run 
Наука
I don't even use Remix on a day-to-day basis but it's always fun to catch Ryan's screencasts :)
I loved your cookie explanations! You kept saying that it was maybe too detailed, but I loved every piece of it. As obvious as it might be for some devs, I'm a senior frontend dev and I had no idea. Just goes to show how much of web standards is hidden away from us nowadays.
I have never used Remix, but I like to see the Web Standards in action (and Ryan is great teacher), so I love watching these videos anyways!
Thank you so much for doing these Remix Singles, been so helpful seeing these things in RemixJS put to practice as I've been building my app 🙌
Although it was not a part of the lesson I find super great that you explained the cookie details like samesite.
Thank you! have a great end of year!
have been using remix for a year now on two big projects and it has been truly amazing 🤩
You explanation is far better than Kent. Trust me.
good Ryan you went into them details too, people can always skip them, but good to see and understand everything you did
Tutorials in remixrun are so helpful , clear and explained.. sometime some funny word make me laughing about typscript ... its mind refreshing. We love remix..
I could listen to Ryan explain the web to me all day. Thankeg senpai
I enjoy the extra details!
Thanks you for this series, really appreciated
actually, samesite explanation was really useful, thx
I could listen to Ryan talk about software development all day
this^
Loving remix
Awesome videos Ryan. I'm in the future, btw. Still no jet packs.
The future is good
question, when the browser cookie (userId) send it to server to validate the user, do you not need to validate again if that userId actually exists or do a server check if that user authenticated via a auth table? or this mechanism is enough to confirm the user is valid?
Good question! You definitely can do that. In my experience I usually need the userId as part of any queries that require authentication, so I don't bother looking up if the userId is valid, since the query itself will fail already
@@ReactTipsWithBrooks how about just say querying data? let’s say data that doesn’t necessarily directly related to the userId. Do you still validate the user if they authenticated in the server or the active userId cookie is sufficient when request is sent?
@@wb9283 I think it depends on your use case a bit. If the data isn't user specific but just requires an authenticated user there's no harm in just validating the user again (except for an extra db lookup, but if that shouldn't be very costly). However, since your server is the only thing that's able to set the value of this cookie it should be sufficient. So it's kind of up to you. Personally I would probably just validate every time in the example you gave, just to be super safe.
@@brookslybrand awesome! thanks so much for the input! Really appreciate your time answering my query (no pun intended 🤣) but yeah, thank you and have a great year ahead!
Hello from the future
what vscode theme is it? also are you using vscodevim?
Github Light
On the theme, I'm not sure. He is using Vim emulation for VSCode though!