title: Laravel catch TokenMismatchException
body: <p>Can the TokenMismatchException be catched using try catch block? Instead of displaying the debug page that shows the "TokenMismatchException in VerifyCsrfToken.php line 46...", I want it to display the actual page and just display an error message.</p>
  
  <p>I have no problems with the CSRF, I just want it to still display the page instead of the debug page.</p>
  
  <p>To replicate (using firefox):
  Steps:</p>
  
  <ol>
  <li>Open page (<a href="http://example.com/login" rel="noreferrer">http://example.com/login</a>)</li>
  <li>Clear Cookies (Domain, Path, Session). I am using web developer toolbar plugin here.</li>
  <li>Submit form.</li>
  </ol>
  
  <p>Actual Results: "Whoops, looks like something went wrong" page displays.
  Expected Results: Still display the login page then pass an error of "Token mismatch" or something.</p>
  
  <p>Notice that when I cleared the cookies, I didn't refresh the page in order for the token to generate a new key and force it to error out.</p>
  
  <p>UPDATE (ADDED FORM):</p>
  
  <pre><code>        &lt;form class="form-horizontal" action="&lt;?php echo route($formActionStoreUrl); ?&gt;" method="post"&gt;
          &lt;input type="hidden" name="_token" value="&lt;?php echo csrf_token(); ?&gt;" /&gt;
          &lt;div class="form-group"&gt;
              &lt;label for="txtCode" class="col-sm-1 control-label"&gt;Code&lt;/label&gt;
              &lt;div class="col-sm-11"&gt;
                  &lt;input type="text" name="txtCode" id="txtCode" class="form-control" placeholder="Code" /&gt;
              &lt;/div&gt;
          &lt;/div&gt;
          &lt;div class="form-group"&gt;
              &lt;label for="txtDesc" class="col-sm-1 control-label"&gt;Description&lt;/label&gt;
              &lt;div class="col-sm-11"&gt;
                  &lt;input type="text" name="txtDesc" id="txtDesc" class="form-control" placeholder="Description" /&gt;
              &lt;/div&gt;
          &lt;/div&gt;
          &lt;div class="form-group"&gt;
              &lt;label for="cbxInactive" class="col-sm-1 control-label"&gt;Inactive&lt;/label&gt;
              &lt;div class="col-sm-11"&gt;
                  &lt;div class="checkbox"&gt;
                      &lt;label&gt;
                          &lt;input type="checkbox" name="cbxInactive" id="cbxInactive" value="inactive" /&gt;&amp;nbsp;
                          &lt;span class="check"&gt;&lt;/span&gt;
                      &lt;/label&gt;
                  &lt;/div&gt;
              &lt;/div&gt;
          &lt;/div&gt;
          &lt;div class="form-group"&gt;
              &lt;div class="col-sm-12"&gt;
                  &lt;button type="submit" class="btn btn-primary pull-right"&gt;&lt;i class="fa fa-save fa-lg"&gt;&lt;/i&gt; Save&lt;/button&gt;
              &lt;/div&gt;
          &lt;/div&gt;
      &lt;/form&gt;
  </code></pre>
  
  <p>Nothing really fancy here. Just an ordinary form. Like what I've said, the form is WORKING perfectly fine. It is just when I stated the above steps, it errors out due to the TOKEN being expired.  My question is that, should the form behave that way? I mean, when ever I clear cookies and session I need to reload the page too? Is that how CSRF works here?</p>