当前位置：文江博客话题详情

ASP.NET 开发服务器 - 403 禁止

发布于 2024-07-10 00:50:06 字数 225 浏览 10 评论 0原文

我正在设置一台新电脑并安装了我的项目以供使用。它是一个.NET Remoting 2.0应用程序，在开发时使用ASP.NET开发服务器来托管服务器端。当我向服务器发出请求时，出现以下错误：

“远程服务器返回错误：(403) 禁止。”

我已检查传入的凭据，一切似乎都是正确的。该调用全部在我的开发盒本地进行，最重要的是。代码没有改变，我所有的同事都工作得很好。有任何想法吗？

原文

分享到QQ

分享到微博

如果你对这篇内容有疑问，欢迎到本站社区发帖提问参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。

发布评论

需要登录才能够评论，你可以免费注册一个本站的账号。

活泼老夫 2024-07-17 00:50:06

好的。我找到了答案……不过，一天中的大部分时间都是这样。事实证明，403 错误是由我们过滤 IP 值的通道接收器提供商之一引发的。通道接收器提供程序是在一些重大假设的情况下编写的。

首先，它会查找调用计算机的地址并将其与 IP 白名单进行比较。作者盲目地收集了列表中的第一个条目：

Dns.GetHostEntry(machineName).AddressList[0].Address

结果在我的新机器上，我启用了 IPv6，所以第一个条目实际上是 IPv6 条目。参考 MSDN 后，我发现 Address 属性现在已“过时”，原因显而易见。

OK. I've found the answer ... better part of a day shot though. Turns out the 403 error is thrown by one of our channel sink providers that filters on IP values. The channel sink provider was written with some big assumptions.

First off, it is looking for the address of the calling machine and comparing it to an ip whitelist. The author blindly gathered the first first entry in the list:

Dns.GetHostEntry(machineName).AddressList[0].Address

Turns out on my new machine, I have IPv6 enabled, so the first entry is actually the IPv6 entry. After referencing the MSDN, I discovered that the Address property is now "Obsolete", for obvious reasons.

回复收藏 0 原文

墨小墨 2024-07-17 00:50:06

错误子代码是什么？

403 - Forbidden. IIS defines several different 403 errors that indicate a more specific cause of the error:
•   403.1 - Execute access forbidden.
•   403.2 - Read access forbidden.
•   403.3 - Write access forbidden.
•   403.4 - SSL required.
•   403.5 - SSL 128 required.
•   403.6 - IP address rejected.
•   403.7 - Client certificate required.
•   403.8 - Site access denied.
•   403.9 - Too many users.
•   403.10 - Invalid configuration.
•   403.11 - Password change.
•   403.12 - Mapper denied access.
•   403.13 - Client certificate revoked.
•   403.14 - Directory listing denied.
•   403.15 - Client Access Licenses exceeded.
•   403.16 - Client certificate is untrusted or invalid.
•   403.17 - Client certificate has expired or is not yet valid.
•   403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.
•   403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.
•   403.20 - Passport logon failed. This error code is specific to IIS 6.0.

What is the error subcode?

403 - Forbidden. IIS defines several different 403 errors that indicate a more specific cause of the error:
•   403.1 - Execute access forbidden.
•   403.2 - Read access forbidden.
•   403.3 - Write access forbidden.
•   403.4 - SSL required.
•   403.5 - SSL 128 required.
•   403.6 - IP address rejected.
•   403.7 - Client certificate required.
•   403.8 - Site access denied.
•   403.9 - Too many users.
•   403.10 - Invalid configuration.
•   403.11 - Password change.
•   403.12 - Mapper denied access.
•   403.13 - Client certificate revoked.
•   403.14 - Directory listing denied.
•   403.15 - Client Access Licenses exceeded.
•   403.16 - Client certificate is untrusted or invalid.
•   403.17 - Client certificate has expired or is not yet valid.
•   403.18 - Cannot execute requested URL in the current application pool. This error code is specific to IIS 6.0.
•   403.19 - Cannot execute CGIs for the client in this application pool. This error code is specific to IIS 6.0.
•   403.20 - Passport logon failed. This error code is specific to IIS 6.0.

回复收藏 0 原文

~没有更多了~