Home/ Questions/Q 8163917
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-06-06T19:10:49+00:00

i asked a question here throw 404 error when route is not satisfied and

  • 0

i asked a question here throw 404 error when route is not satisfied and getting the answer, i thought: is the design i choosed a good one, so i decided to post it as a separate question:

what do you think is a better solution: hardcode 100 routes for every page in my webapplication and one catch all route to redirect to the 404 page, or hardcode 1 ‘generic’ route and catch all ‘wrong’ url’s in the error handler?

The ‘problem’ with the latter is that when the app is flooded with bad urls, the app will throw (expensive as i always read) loads of exceptions….

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Having too many routes is also inefficient, specially for URL generation. You can:

    1. Use a base Controller and override HandleUnknownAction, so it doesn’t throw an exception.
    2. Instead of creating a route for each action you can group similar routes and use constraints for the controller and action tokens. A tool like MvcCodeRouting can help you automate this.
    • 0