404 issue with Laravel route

Question

I am very confused as to why this is happening but here is the issue guys. Basically I am building an app using laravel4 I want to go to this URL

http://app.tld/books

However I get this error every time:

404: The requested URL /books was not found on this server.

However in my routes.php file I have the route defined:

Route::get('/books', 'BookController@index');

I also have a view and relevent method in Controller:

public function index(){
        $books = Book::all();
        return View::make('book.index')->with('books', $books);
    }

In your vhost, do you have it pointing to the /public directory of the project, or just the project root? — Jeff Lambert
– Jeff Lambert, Commented Aug 18, 2014 at 18:41
Have you ran php artisan dump-autoload ? Maybe Laravel didn't yet see your BookController. — user2629998
– user2629998, Commented Aug 18, 2014 at 18:42
Probably you need to run php artisan dump-autoload from command prompt/terminal. — The Alpha
– The Alpha, Commented Aug 18, 2014 at 18:42
Yes it is pointing to /public and also ran the dump auto-load it is strange because in work I can run the project no problem. I've checked it out using SVN into Netbeans — Javacadabra
– Javacadabra, Commented Aug 18, 2014 at 18:43

Community · Accepted Answer · 2017-05-23 12:11:40Z

From the comments we gather that it was an Apache issue, not a Laravel issue (mod_rewrite wasn't enabled -- kudos to @watcher), and I'm glad you sorted it out.

For future reference, it seemed likely to be an Apache issue because Laravel throws PHP exceptions on undefined routes, namely a Symfony \ Component \ HttpKernel \ Exception \ NotFoundHttpException. If you have debug set to true you'll get a neatly styled stack trace with code highlighting and server/request data, if not you'll get a neatly styled "Whoops, looks like something went wrong." message. If, on the other hand, you get a white screen with Times New Roman messages like "404: The requested URL /books was not found on this server.", Laravel isn't even starting up.

As the comments on your question show, there are many other clues which will tell you that it's not your Laravel routes, though from the code you posted and even the title of the question, you seemed to had narrowed it down to routes, which probably had you looking in the wrong place for a while.

Collectives™ on Stack Overflow

404 issue with Laravel route

1 Answer 1

Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related