CSRF Protection in Laravel

In this video, I'm going to explain how Cross-site request forgery happens and how Laravel helps you protect your application from it.

[@sir_brian_d]

You explain things so well. You're a great teacher

[@themsaid]

Thanks! Glad you found it useful :)

[@MuhammadMohsen]

Audio is fine now, Good job dude.

[@joshmountain]

Thanks Mohamed! Very straightforward and easy to understand. The only thing I believe was left out was when and how CSRF tokens are rerolled - is a new token generated and stored in the session for each request?

[@themsaid]

The CSRF token is rolled whenever the session is rolled. So if you have the session lifetime set to 2 hours (the default) and the user stayed idle for 2 hours, the token will expire on his next request and he'll need to refresh to get the new token.

[@hambaku7318]

Thanks for video, very helpful!

[@mikeziri]

nice sound!
good explaining ;)

[@themsaid]

Glad you liked it :)

[@izzudinanuar7867]

That really helpful

[@lianglaw6923]

Yeah, thanks for your contribution. Mohammed.

[@themsaid]

Welcome :)

[@dinhquochan]

It's better. Congrats!

[@themsaid]

Finally :D

[@alexios4392]

:) so with Laravel Sanctum can we use both - CSRF-Token from meta tag and XSRF-Token from cookies? Does it matter?

[@a7medsayed2010]

i think that you mentioned before that cookies are encrypted then how axios extracts csrf token from them ?

[@themsaid]

axios send the encrypted CSRF token, Laravel decrypts it before verification.

[@a7medsayed2010]

Many thanks keep going

[@YunusIs]

Audio is much better on this video.

[@themsaid]

Thanks for the feedback :)