IIS代理/传递问题
我们有一组计算机需要访问托管在 ASP.NET 盒子上的特定 Web 应用程序 (MVC)。这些计算机位于自己的小子网上，只能看到控制它们的小型后台服务器。
反过来，该服务器可以看到我们网络的整个其余部分，包括有问题的 ASP.NET 框。
我需要弄清楚如何使用中间服务器上的 IIS 向这些计算机发送来自 ASP.NET 框的请求。我不确定是否需要代理，或者是否有办法仅通过 IIS 来完成此操作。感谢任何和所有的帮助。谢谢！
We have set of computers that need to access a certain web application (MVC) hosted on our ASP.NET box. These computers are on their own little subnet that can only see a small back office server that controls them.
That server, in turn, can see the entire rest of our network including the ASP.NET box in questions.
What I need to figure out is how to use IIS on the middle server to send requests to and from the ASP.NET box to these computers. I'm not sure if I need a proxy or if there is a way to do this soley through IIS. Any and all help is appreciated. Thanks!
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
我意识到这是一个相当老的问题，但我认为值得回答。 IIS 不一定是此处选择的最佳技术，因为它旨在提供服务，而不是中继服务。
但是，如果您确实想使用 IIS，您可以安装 Helicon Tech 的 ISAPI Rewrite 这样的产品，它支持通过 IIS 代理网站，只需很少的配置。但是，这将使用服务器上的宝贵资源来解决可能不值得的问题。
根据我的理解，您拥有两个网络（父网络和子“安全”网络），并且它们都位于不同的子网上，但位于内部，您应该能够使用您最喜欢的计算机供应商店中的标准路由器来充当桥。可以告诉路由器允许访问安全网络上的特定端口/IP 组合，但不允许访问其他端口/IP 组合。此配置因路由器而异，但概念是相同的。在 Cisco ASA5505 等功能更强大的路由器上，您可以非常轻松地桥接不同物理端口上的多个子子网（具有任意权限/限制组合），同时维护用于互联网访问的相同公共接口。拥有这样的专用路由器将比通过共享服务器进行代理提供更高的性能和可靠性，并且在我看来更好的安全控制。
最重要的是，您有多种选择来解决您的问题，但我个人的偏好是在使用 IIS 作为代理服务器之前调整网络体系结构/路由器以满足您的需求。
I realize this is a rather old question, but I thought worth answering. IIS is not necessarily the best technology of choice here as it is intended to provide a service, not so much to relay a service.
However, if you really wanted to use IIS you can install a product like Helicon Tech's ISAPI Rewrite which supports the proxying of websites through IIS with very little configuration. However, this will be using valuable resources on your server for a problem that may not merit it.
Given my understanding that you own both networks (the parent network and the child "secure" network) and that they are both on different subnets but internal, you should be able to use a standard router from your favorite computer supply store to act as the bridge. The router can be told to allow access to a specific port/IP combo on the secure network but no others. This configuration will vary from router to router, but the concept is the same. On a more capable router like a Cisco ASA5505 you can very easily bridge accross multiple child subnets on different physical ports (with any combination of permissions/restrictions) while maintaining the same public interface for internet access. Having a dedicated router like this will provide much greater performance and reliability than proxying through a shared server and IMO better security control.
Bottom line is that you have multiple options for solving your problem, but my personal preference would be to adjust the network architecture/router to accomodate your needs before I would use IIS as a proxy server.