#1
  1. I lov C in AIX/Linux, hate C++
    Devshed Intermediate (1500 - 1999 posts)

    Join Date
    Jul 2003
    Location
    Jacksonville, Florida
    Posts
    1,655
    Rep Power
    34

    Routes.MapPageRoute("route1","support","~/Support.aspx") does not work, why?


    I noticed trying to route the url to a physical webpage does not work. ASP.NET does not like the use of routeUrl "support".

    Code:
    routes.MapPageRoute("route1","support","~/Support.aspx")
    but works when others is used...

    Code:
    routes.MapPageRoute("route2","contact","~/ContactUs.aspx")
    routes.MapPageRoute("route3","about","~/AboutUs.aspx")
    routes.MapPageRoute("route4","features","~/Features.aspx")
    What can I do to make it work for the Support webpage?

    P.S. Using "support" routeUrl, in Visual Studio debugger, it returned a file not found error but on production environment, it returned a "Directory Listing Denied" error. But when I typed in Support.aspx in the web browser's url, it showed a webpage.
    Last edited by fletchsod; August 29th, 2012 at 11:06 AM.
  2. #2
  3. I lov C in AIX/Linux, hate C++
    Devshed Intermediate (1500 - 1999 posts)

    Join Date
    Jul 2003
    Location
    Jacksonville, Florida
    Posts
    1,655
    Rep Power
    34
    Appearantly, there's a folder name "support" that stored the exe files. So, it conflict w/ the routeUrl.

    The workaround to the problem is to add this to the script...

    routes.RouteExistingFiles = true;

IMN logo majestic logo threadwatch logo seochat tools logo