ASP.NET Controller name conflicted with a folder name

Question

In my ASP.NET MVC3 project, I have a folder called Content (the default folder for an MVC project). But I also have a controller called Content. And when I want to use the default actions of this controller, I simply use http://domain/content/, which is equivalent to http://domain/content/index. But IIS returns 403 error and thinks that I'm gonna get the directory list of the Content Folder. Well, this question is already discussed in this question. But I don't know how to rewrite my URL to append the default action to it. May someone help please.

Just avoid using the same names, now you're getting into unnecessary problems that could be avoided other ways. Just rename you Content folder to public or something similar. — mare
– mare, Commented Jul 10, 2011 at 19:16
Well, I know that. But my question is a general case. What if you encounter a real name collision? Anyway, thank you for mentioning. — Saeed Neamati
– Saeed Neamati, Commented Jul 10, 2011 at 19:17

David Kirkland · Accepted Answer · 2013-10-26 20:56:20Z

7

You can get around this by changing routing configuration to specify:

routes.RouteExistingFiles = true;

You will then need to set up some ignore rules to prevent genuine static content being gobbled up by the routing engine.

For example, I have a folder called Touch in my app, and I also have a specific route for Touch. So the working config is:

routes.RouteExistingFiles = true;
routes.IgnoreRoute("Touch/Client/{*touchclientversion}", new { touchclientversion = @"(\d*)(/*)" });

I agree that this kind of thing should generally be avoided, but sometimes it's nice to have pretty URLs :-)

answered Oct 26, 2013 at 20:56

David Kirkland

2,46128 silver badges28 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Mrchief · Accepted Answer · 2011-07-10 19:09:39Z

0

You can add a default route like this:

routes.MapRoute(
                "Default",                                              // Route name
                "{controller}/{action}/{id}",                           // URL with parameters
                new { controller = "Home", action = "Index", id = "" }  // Parameter defaults
            );

In your case:

routes.MapRoute(
                "DefaultContent",                                              // Route name
                "{controller}/{action}/{id}",                           // URL with parameters
                new { controller = "Content", action = "Index", id = "" }  // Parameter defaults
            );

answered Jul 10, 2011 at 19:09

Mrchief

76.4k20 gold badges145 silver badges193 bronze badges

2 Comments

Saeed Neamati Over a year ago

Downvote, because I said that I want to rewrite the incoming URL before it maps to route rules. I already have those route rules in action. But IIS StaticHandler takes precedence in responding.

Mrchief Over a year ago

How about mentioning that in the post? Sorry, my mind scanner is not working today.

Collectives™ on Stack Overflow

ASP.NET Controller name conflicted with a folder name

2 Answers 2

Comments

2 Comments

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

2 Comments

Your Answer

Sign up or log in

Post as a guest

Linked

Related