Is DocumentationController reserved for system usage or something?
I created a blank MVC app, created a DocumentationController with corresponding view. It works if I go to www.mysite.com/Documentation/Index but if I go to www.mysite.com/Documentation/ then I get a 403 forbidden.
Renaming DocumentationController to Documentation2Controller and associated views, it (the default route, etc.) works perfectly.
Is it a reserved keyword or could there be another reason why it doesn't pick up the default route?
Make sure you don't have an actual virtual/physical directory named Documentation.
You can also instruct MVC to 'take over' the request even when it matches a directory by setting the RouteExistingFiles flag to true (in your Routes configuration):
public static void RegisterRoutes(RouteCollection routes)
{
routes.RouteExistingFiles = true;
//...
}
Collected from the Internet
Please contact [email protected] to delete if infringement.
Comments