Question

On my web site I previously had a page located at "/careers". I recently decided to rename this page to "/jobs". Now when I try to access this page on my published Azure Web Site I just get a 403 response with the following error:

You do not have permission to view this directory or page.

It works on my local dev machine, and it works if I rename the action to "jobs". Why am I not allowed to create a route called "jobs"? Is this reserved in Azure for some bizarre reason?

// Does not work
public ActionResult Jobs()
{
    return View("jobs");
}

// Does work
public ActionResult Jobs2()
{
    return View("jobs");
}

From what I can tell, my routes should not be preventing me from using this action, and I don't have any sub-directories called "Jobs" in either my Views folder or my Controllers folder.

Edit:

I just noticed that the issue is not actually "/jobs", but rather "/jobs/". For some reason Chrome was redirecting me to "/jobs/" (probably due to history). I tried the same for other routes and it works fine.

/features (works)
/features/ (works)
/jobs (works)
/jobs/ (does not work)
Was it helpful?

Solution

By accessing my site on Azure with FTP I was now able to see that there in fact was a "jobs" folder uploaded on Azure (files left behind by an older version of the website).

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top