I've decided to split up my users logic into a controller to clean up my routes file, going down the RESTful route i've got something like:

```
UsersController {
    getLogin() {
    }
    postLogin() {
    }
}

```

Only now i'm stick with /users/login and /users/register etc..

I need to change them to /login and /register, i've researched and not found a definitive answer, i tried the named route method:

```
Route::get('users/login', array('as' => 'login', 'uses' => 'UsersController@getLogin'));

```

But it says not found, after a bit of T&E i found a working route:

```
Route::get('login', 'UsersController@getLogin');

```

Only now i'm explicitly defining every method.. does this defeat the object of RESTful when i'm defining the verb twice?

It would be awesome if Laravel could work out what method is being requested then i could do something like the following and be done with:

```
Route::any('login', 'UsersController@Login');

```

As far as i know, this can't be done... so is it pointless trying to work RESTful in this situation and should just use named routing for all my methods?