title: Questions about the principle of routes matching in Kong
body: <p>I have some problems when using Kong to configure routing .I need to apply the login authentication plug-in to the specified api path.</p>
  <p>For example,</p>
  <ul>
  <li>If there is a Route named ‘Route1’ and it’s path is '<code>/api/phone</code>',</li>
  <li>I want to apply the authentication plug-in to all requests under the path of '<code>/api/phone/sell</code>'.
  So I built a Route named ‘Route2’ with path:'<code>/api/phone/sell</code>'.</li>
  </ul>
  <p>But when I actually called it, it was different from what I expected.</p>
  <p>When my request path is '<code>/api/phone/sell</code>', the matched Route is ‘Route1’. Only when my request path is '<code>/api/phone/sell/abc</code>' can I match ‘Route2’.</p>
  <p>This has caused me confusion, because I recently upgraded my version of kong from 0.14.x to 1.3.x, and there was no such problem in the previous version. Is it because I don’t understand the path matching principle correctly, or is there some adjustments in Kong after a certain version?</p>
  <p>All help appreciated!</p>