HTTP错误403.14 - 在访问网站时,禁止故障 [英] HTTP Error 403.14 - Forbidden Error when accessing website

查看:947
本文介绍了HTTP错误403.14 - 在访问网站时,禁止故障的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

所以,我把所有的更新code,整个解决方案的基础之上。它适用于其他人的机器,但是当我试图访问本地主机/外网我的机器上,它给了我这个错误:

So I have all the updated code, the entire solution builds. It works on everyone else's machine, however when I try and access localhost/extranet on my machine, it gives me this error:

HTTP错误403.14 - 禁止

HTTP Error 403.14 - Forbidden

详细的错误信息:

Module DirectoryListingModule
Notification ExecuteRequestHandler
Handler 0x00000000
Requested URL   http://localhost:80/extranet/
Physical Path C:\svn\K2\trunk\appteam\web\Chatham.Web.UI.Extranet\
Logon Method Anonymous
Logon User Anonymous

现在我试着进入IIS7,并启用目录浏览,删除这个错误,但还是没有打开我的网站。我也尝试进入和禁用默认文档,重新启用它,一切,毫无效果。我也重新启动IIS几次都没有结果。

Now I tried going into IIS7, and enabling directory browsing, this removed the error, but still didn't bring up my website. I also tried going in and disabling the default document, re-enabling it, everything, nothing worked. I've also restarted IIS a few times to no avail.

任何想法?

推荐答案

这听起来像你的IIS不处理您的应用程序的路由规则,并试图找到一个Default.aspx的,index.htm的,等等。由于它不能,它是想显示目录列表(这就是为什么你都拿到了404.14)。

It sounds like your IIS is not processing the routing rules for your application and is trying to find a default.aspx, index.htm, etc. Since it cannot, it is wanting to display the directory listings (which is why you were getting the 404.14).

我只是检查我的dev的设置和我的认为的,你的程序池,必须综合设置,而不是经典的托管管道的程序池。我也遇到了这个之前,有很多方法可以使用​​经典管道,但这会/应该是解决问题的最快捷方式。要检查/更改管道模式,点击应用程序池从IIS左侧的菜单中,找到你的应用程序池,并期待在托管管道列。如果它被设置为经典 - >右键单击该程序池,选择基本设置,然后从经典的下拉菜单切换到集成

I just checked my dev setup and I think that your AppPool has to be set on Integrated as opposed to Classic on the Managed Pipeline for the AppPool. I have ran into this before, there may be ways to use the Classic Pipeline, but this would/should be the quickest way to resolve your issue. To check/change the pipeline mode, click on Application Pools from the menu on the left side of IIS, find your AppPool and look in the managed pipeline column. If it is set to Classic -> Right click the AppPool, choose basic settings, then change the dropdown from Classic to Integrated.

如果我不正确,有人请随时纠正我对这个的意见。

If I am incorrect, someone please feel free to correct me on this in the comments.

修改的 - 我想补充,可以运行在经典管道模式的MVC应用程序,但你必须做的IIS 6的技巧来得到它才能正常工作。主要是,你需要打开通配符脚本映射MVC在经典模式下工作,如果不是,它预计在.aspx文件(或类似)的存在,因为它从IIS在处理执行管线.NET。

Edit - Just to add, you can run an MVC app in the Classic Pipeline mode, but you have to do the IIS 6 tricks to get it to work properly. Mainly, you need to turn on wildcard script mapping for MVC to work in Classic mode, If not it expects an .aspx file (or similar) to exist for it to handle the execution pipeline over to .NET from IIS.

这篇关于HTTP错误403.14 - 在访问网站时,禁止故障的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆