Question: My Laravel 4 application's logs sometimes show a `NotFoundHttpException`:

```
exception 'Symfony\Component\HttpKernel\Exception\NotFoundHttpException' in /var/www/laravel4/bootstrap/compiled.php:7420
Stack trace:
#0 /var/www/laravel4/bootstrap/compiled.php(7137): Illuminate\Routing\Router->handleRoutingException(Object(Symfony\Component\Routing\Exception\ResourceNotFoundException))
#1 /var/www/laravel4/bootstrap/compiled.php(7113): Illuminate\Routing\Router->findRoute(Object(Illuminate\Http\Request))
#2 /var/www/laravel4/bootstrap/compiled.php(958): Illuminate\Routing\Router->dispatch(Object(Illuminate\Http\Request))
#3 /var/www/laravel4/bootstrap/compiled.php(946): Illuminate\Foundation\Application->dispatch(Object(Illuminate\Http\Request))
#4 /var/www/laravel4/public/index.php(49): Illuminate\Foundation\Application->run()
#5 {main}

```

What could have caused this? The stack trace doesn't show anything from my code.

Answer: 
It's really hard to say for sure what is causing this without knowing your code. Looking at the stack trace of the error, it's clear that the Router is dispatching it and I guess it has nothing to do with the background job itself, but rather the API's it calls.

In your specific case, the exception is throw after a [ResourceNotFoundException](https://symfony2-document.readthedocs.org/en/latest/components/routing.html), which happens when there's no route defined for such URL pattern.

**Possible problems:**

If the background job does a `file_get_contents` or `curl` on your own API's, it may be calling a route that does not exist and then throwing that exception.

If you don't have control of the URL's the background job is downloading, it may be trying to fetch an URL like `127.0.0.1`, `localhost` or anything like that.
I got this error because i used method="post" in my form instead of method="POST". 

Might be useful to someone.