Laravel - Session store not set on request

Question

I recently created a new Laravel project and was following along the guide on Authentication  When I visit either my login or register route  I get the following error   ErrorException in Request php line 775  Session store not set on request   View  C  Users Matthew Documents test resources views auth register blade php    I haven t edited any core Laravel files  I ve only created the views and added the routes to my routes php file     Authentication routes Route  get  auth login     uses    gt   Auth AuthController getLogin    as    gt   login     Route  post  auth login     uses    gt   Auth AuthController postLogin    as    gt   login     Route  get  auth logout     uses    gt   Auth AuthController getLogout    as    gt   logout         Registration routes Route  get  auth register     uses    gt   Auth AuthController getRegister    as    gt   register     Route  post  auth register     uses    gt   Auth AuthController postRegister    as    gt   login       I don t have much experience with Laravel  so please excuse my ignorance  I m aware that there is another question asking this same thing  but neither of the answers seem to work for me  Thanks for reading   Edit   Here s my register blade php as requested    extends  partials main     section  title    Test   Register     section  content        lt form method  POST  action   auth register  gt              csrf field                lt div class  ui input  gt             lt input type  text  name  name  value     old  name       placeholder  Username  gt           lt  div gt           lt div class  ui input  gt             lt input type  email  name  email  value     old  email       placeholder  Email  gt           lt  div gt           lt div class  ui input  gt             lt input type  password  name  password  placeholder  Password  gt           lt  div gt           lt div class  ui input  gt             lt input type  password  name  password confirmation placeholder  Confirm Password  gt           lt  div gt           lt div gt               lt button class  ui primary button  type  submit  gt Register lt  button gt           lt  div gt       lt  form gt   endsection

User · Answer

Laravel 5 3   web middleware group is automatically applied to your routes web php file by the RouteServiceProvider    Unless you modify kernel  middlewareGroups array in an unsupported order  probably you are trying to inject requests as a regular dependency from the constructor   Use request as  public function show Request  request        instead of   public function   construct Request  request

User · Answer

Do you can use - gt stateless   before the - gt redirect    Then you dont need the session anymore

User · Answer

In my case  using Laravel 5 3  adding only the following 2 middleware allowed me to access session data in my API routes     App Http Middleware EncryptCookies  class  Illuminate Session Middleware StartSession  class   Whole declaration   middlewareGroups in Kernel php     api    gt                 App Http Middleware EncryptCookies  class               Illuminate Session Middleware StartSession  class               throttle 60 1                bindings

User · Answer

If adding your routes inside the web middleware doesn t work for any reason then try adding this to  middleware into Kernel php  protected  middleware                            Illuminate Session Middleware StartSession  class           Illuminate View Middleware ShareErrorsFromSession  class

User · Answer

If you are using CSRF enter  before   gt  csrf   In your case Route  get  auth login     before   gt  csrf   uses    gt   Auth AuthController getLogin    as    gt   login      For more details view Laravel 5 Documentation Security Protecting Routes

User · Answer

If Cas Bloem s answer does not apply  i e  you ve definitely got the web middleware on the applicable route   you might want to check the order of middlewares in your HTTP Kernel   The default order in Kernel php is this    middlewareGroups          web    gt             App Http Middleware EncryptCookies  class           Illuminate Cookie Middleware AddQueuedCookiesToResponse  class           Illuminate Session Middleware StartSession  class           Illuminate View Middleware ShareErrorsFromSession  class           App Http Middleware VerifyCsrfToken  class              Note that VerifyCsrfToken comes after StartSession  If you ve got these in a different order  the dependency between them can also lead to the Session store not set on request  exception

User · Answer

in my case it was just to put  return    at the end of function where  i have set session

User · Answer

A problem can be that you try to access you session inside of your controller s    constructor   function   From Laravel 5 3  this is not possible anymore because it is not intended to work anyway  as stated in the upgrade guide      In previous versions of Laravel  you could access session variables or   the authenticated user in your controller s constructor  This was   never intended to be an explicit feature of the framework  In Laravel   5 3  you can t access the session or authenticated user in your controller s constructor because the middleware has not run yet    For more background information also read Taylor his response   Workaround  If you still want to use this  you can dynamically create a middleware and run it in the constructor  as described in the upgrade guide      As an alternative  you may define a Closure based middleware directly   in your controller s constructor  Before using this feature  make sure   that your application is running Laravel 5 3 4 or above    lt  php  namespace App Http Controllers   use App User  use Illuminate Support Facades Auth  use App Http Controllers Controller   class ProjectController extends Controller                  All of the current user s projects              protected  projects                  Create a new controller instance                 return void             public function   construct                  this- gt middleware function   request   next                 this- gt projects   Auth  user  - gt projects               return  next  request

User · Answer

Laravel  5 4   My solution was to use global session helper  session    Its functionality is a little bit harder than  request- session     writing   session   key   gt  value       pushing   session  - gt push  key    notification     retrieving   session  key

User · Answer

I was getting this error with Laravel Sanctum  I fixed it by adding  Illuminate Session Middleware StartSession  class  to the api middleware group in Kernel php  but I later figured out this  worked  because my authentication routes were added in api php instead of web php  so Laravel was using the wrong auth guard   I moved these routes here into web php and then they started working properly with the AuthenticatesUsers php trait   Route  group   middleware    gt    guest    throttle 10 5     function          Route  post  register    Auth RegisterController register  - gt name  register        Route  post  login    Auth LoginController login  - gt name  login         Route  post  password email    Auth ForgotPasswordController sendResetLinkEmail        Route  post  password reset    Auth ResetPasswordController reset         Route  post  email verify  user     Auth VerificationController verify  - gt name  verification verify        Route  post  email resend    Auth VerificationController resend         Route  post  oauth  driver     Auth OAuthController redirectToProvider  - gt name  oauth redirect        Route  get  oauth  driver  callback    Auth OAuthController handleProviderCallback  - gt name  oauth callback         Route  post  logout    Auth LoginController logout  - gt name  logout      I figured out the problem after I got another weird error about RequestGuard  logout   does not exist   It made me realize that my custom auth routes are calling methods from the AuthenticatesUsers trait  but I wasn t using Auth  routes   to accomplish it  Then I realized Laravel uses the web guard by default and that means routes should be in routes web php   This is what my settings look like now with Sanctum and a decoupled Vue SPA app   Kernel php  protected  middlewareGroups          web    gt             App Http Middleware EncryptCookies  class           Illuminate Cookie Middleware AddQueuedCookiesToResponse  class           Illuminate Session Middleware StartSession  class              Illuminate Session Middleware AuthenticateSession  class           Illuminate View Middleware ShareErrorsFromSession  class           App Http Middleware VerifyCsrfToken  class           Illuminate Routing Middleware SubstituteBindings  class               api    gt            EnsureFrontendRequestsAreStateful  class           Illuminate Routing Middleware SubstituteBindings  class           throttle 60 1                  Note  With Laravel Sanctum and same-domain Vue SPA  you use httpOnly cookies for session cookie  and remember me cookie  and unsecure cookie for CSRF  so you use the web guard for auth  and every other protected  JSON-returning route should use auth sanctum middleware    config auth php   defaults    gt         guard    gt   web        passwords    gt   users             guards    gt         web    gt             driver    gt   session            provider    gt   users                api    gt             driver    gt   token            provider    gt   users            hash    gt  false              Then you can have unit tests such as this  where critically  Auth  check    Auth  user    and Auth  logout   work as expected with minimal config and maximal usage of AuthenticatesUsers and RegistersUsers traits   Here are a couple of my login unit tests   TestCase php         Creates and or returns the designated regular user for unit testing        return  App User     public function user     User        user   User  query  - gt firstWhere  email    test-user example com         if   user            return  user                User  generate   is just a wrapper around User  create        user   User  generate  Test User    test-user example com   self  AUTH PASSWORD        return  user            Resets AuthManager state by logging out the user from all auth guards     This is used between unit tests to wipe cached auth state         param array  guards     return void     protected function resetAuth array  guards   null    void        guards    guards    array keys config  auth guards          foreach   guards as  guard             guard    this- gt app  auth  - gt guard  guard            if   guard instanceof SessionGuard                 guard- gt logout                          protectedProperty   new  ReflectionProperty  this- gt app  auth     guards         protectedProperty- gt setAccessible true        protectedProperty- gt setValue  this- gt app  auth             LoginTest php  protected  auth guard    web         test    public function it can login          user    this- gt user          this- gt postJson route  login      email    gt   user- gt email   password    gt  TestCase  AUTH PASSWORD           - gt assertStatus 200          - gt assertJsonStructure                user    gt                       expectedUserFields                                   this- gt assertEquals Auth  check    true        this- gt assertEquals Auth  user  - gt email   user- gt email        this- gt assertAuthenticated  this- gt auth guard        this- gt assertAuthenticatedAs  user   this- gt auth guard         this- gt resetAuth            test    public function it can logout          this- gt actingAs  this- gt user            - gt postJson route  logout            - gt assertStatus 204         this- gt assertGuest  this- gt auth guard         this- gt resetAuth        I overrided the registered and authenticated methods in the Laravel auth traits so that they return the user object instead of just the 204 OPTIONS   public function authenticated Request  request  User  user        return response  - gt json            user    gt   user             protected function registered Request  request  User  user        return response  - gt json            user    gt   user              Look at the vendor code for the auth traits  You can use them untouched  plus those two above methods    vendor laravel ui auth-backend RegistersUsers php vendor laravel ui auth-backend AuthenticatesUsers php   Here is my Vue SPA s Vuex actions for login   async login   commit    credentials        try           const   data     await axios post route  login                     credentials              remember  credentials remember    undefined                       commit FETCH USER SUCCESS    user  data user             commit LOGIN            return commit CLEAR INTENDED URL         catch  err            commit LOGOUT           throw new Error  auth login  Problem logging user in    err                async logout   commit          try           await axios post route  logout              return commit LOGOUT         catch  err            commit LOGOUT            throw new Error  auth logout  Problem logging user out    err                 It took me over a week to get Laravel Sanctum   same-domain Vue SPA   auth unit tests all working up to my standard  so hopefully my answer here can help save others time in the future

User · Answer

It s not on the laravel documentation  I have been an hour to achieve this   My session didn t persist until i used the  save  method      request- gt session  - gt put  lang   en EN     request- gt session  - gt save

User · Answer

I m using laravel 7 x and this problem arose   the following fixed it  go to kernel php and add these 2 classes to  protected  middleware  Illuminate Session Middleware StartSession  class   Illuminate View Middleware ShareErrorsFromSession  class

User · Answer

You ll need to use the web middleware if you need session state  CSRF protection  and more   Route  group   middleware    gt    web     function             your routes here

User · Answer

In my case I added the following 4 lines to  middlewareGroups  in app Http Kernel php     api    gt         App Http Middleware EncryptCookies  class       Illuminate Cookie Middleware AddQueuedCookiesToResponse  class       Illuminate Session Middleware StartSession  class       App Http Middleware VerifyCsrfToken  class       throttle 60 1        bindings        IMPORTANT  The 4 new lines must be added BEFORE  throttle  and  bindings    Otherwise a  CSRF token not match  error will rise  I ve struggled in this for several hours just to find the order is important   This allowed me to access session in my API  I also added VerifyCsrfToken as when cookies sessions are involved  CSRF needs to be taken care of

[php] Laravel - Session store not set on request

Examples related to php

Examples related to laravel