title: laravel 5 nested routing issue
body: <p>New to Laravel 5, and building a little Rest test app.  So I'm envisioning 2 different endpoints for a single controller.</p>
  
  <pre><code>/myApp/public/index.php/states/{state}/cities  //returns cities in a state
  </code></pre>
  
  <p>and </p>
  
  <pre><code>/myApp/public/index.php/states/{state}/cities/{city}  //will do somethin else
  </code></pre>
  
  <p>its a little unclear to me how to set up the routes for this.  I suppose I could have these endpoints use the same controller method, but it seems like better architecture to just route each to its own method.</p>
  
  <p>So far, I've got 2 things that each individually work, but dont work together:</p>
  
  <p>in routes.php</p>
  
  <pre><code>//route to the first endpoint
  Route::resource('states.cities', 'StatesController');
  //routes to the second endpoint if first is uncommented,otherwise blank page with no errors in log
  Route::resource('states.cities', 'StatesController@cities');
  </code></pre>
  
  <p>And the relevant part of my controller code:</p>
  
  <pre><code>class StatesController extends Controller
  {
      /**
       * Display a listing of the resource.
       *
       * @return Response
       */
      public function index(Request $request, $state)
      {
          //works
          $cities = States::where('state', '=', $state)-&gt;lists('name');
          echo json_encode($cities);
      }
  
  
      public function cities(Request $request, $state, $city)
      {
          echo "second request";
          echo $state;
          echo $city;
      }
      ......
  </code></pre>
  
  <p>Any one have any ideas on the proper way to handle this going forward?  Cheers!</p>