title: ASP.NET Core 3 MVC Route Debugging
body: <p>What methods are available for debugging routing issues in ASP.NET Core 3.1 Web API? Specifically, the infamous 404. </p>
  
  <p>I've seen tons of questions regarding this in a Web API but they all deal with the specific problems of the individual. What I am looking for is a systematic way of determining how/why my url matched or failed to match each route in the route collection.  </p>
  
  <p>Unfortunately, the logging output, even when set to Trace, only shows:</p>
  
  <pre><code>Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request starting HTTP/2.0 GET https://localhost:5000/Ctrlr/Action  
  Microsoft.AspNetCore.Hosting.Internal.WebHost:Information: Request finished in 8.4141ms 404   
  </code></pre>
  
  <p>Phil Haack's routedebugger for classic ASP.NET MVC was a wonderful tool but I don't believe that it can be used in .NET Core 3. </p>
  
  <p>I feel like I'm missing something huge but I have looked without success. </p>
  
  <p>Thanks </p>