Migrating from .NET Core 3.1 to .NET 5, we encountered peculiar behavior with a catch-all route configuration.
The relevant part of the startup configuration looks like t
