🛠️ 419 Diagnostics

Run these in order. Anything red is the cause of your 419.

{{-- 1. Session driver/config snapshot — auto-fetched + auto-flagged --}}

1. Session + environment snapshot

🔴 Likely cause(s) of your 419:
✅ No obvious config problems detected — likely something else (see test 3). 

        
Loading…


        

            Also visible directly: /__diag/session — paste back to me if needed.
        

    


    {{-- 2. CSRF token --}}
    

        
2. CSRF token reachable

        

            /__diag/csrf should return a 40-char token.
        

        
Current page's token: {{ csrf_token() }}

    


    {{-- 3. POST + CSRF live test --}}
    

        
3. POST with CSRF (the real test)

        
Click "Test POST". A 200 means CSRF works — your 419 is something else (e.g. file too big). A 419 means session/cookie/CSRF setup is broken.


        

            @csrf
            
            
        


        


        
3b. POST with file upload (multipart/form-data)

        

            @csrf
            
            
            
        

        
If text-only POST returns 200 but file upload returns 419 → it's PHP post_max_size / upload_max_filesize, not CSRF.

    


    

        ⚠️ Remove these routes after fixing.
        Comment out the /__diag/* block in routes/web.php when you're done.