Weird Random Laravel Errors - CSRF, NotFoundException, Access Denied...
I've been working with Laravel the last couple of months and there are a few issues I run into randomly. "Randomly" is the key operative here because they don't happen every time.
I'll keep getting a TokenMismatchException from time to time while trying to submit a form or paging through an AJAX Datatable. This happens once too often and has me wanting to remove the CSRF middleware but would do that only as a last resort if there no real solution. I am using the recommended set up of passing a _token in the meta and using Ajax set up to pass the headers.
Sometimes when doing quick refreshes either manually or by AJAX or even sometimes just normally, I'll get a Route NotFoundException but after a refresh it comes back up. Not sure why that would happen. This is rare but has happened more so since I've upgraded to 5.1 yesterday.
I just faced a weird error right now, where I got this:
Access denied for user ''@'localhost' to database 'forge'
But on refresh, it went away. Not sure why that would come. I have nothing to do with forge, never used it.
Am I the only one with these issues? Are there known solutions. I've seen a LOT of CSRF threads but haven't found a definitive solution yet to that. The other two, I haven't found much info, so guessing it's just too random? But when the randomness becomes too often, it's a bit of a problem.
Issues #2 and #3 above seem to only happen in my local set up with Windows and XAMPP but I have not found such issues on the production server. So if anyone does find this issue occurring with them, it seems to be related to the environment configuration.
Issue #3 occurs when multiple AJAX requests are sent in quick succession and for some reason the local db server is not able to keep up with the load and that's when this error comes. Not sure why this error of "access denied to forge" is thrown but it's just the way it is.
Issue #2 - not sure why, it's as if the application hasn't loaded/compiled fully before the server returns the page. This happens rarely (has occurred 3 times so far in the last 2 days after the upgrade and using the site for multiple hours) but seems specific to my local environment for now. Although this issue has come about only after 5.1, never faced it in the last couple of months of working with 5.0.*
As for the CSRF issue, have yet to test for this error on the production environment, so can't comment on that as yet...
