将虚拟目录映射到 ASP.NET MVC 操作
对于我们的新闻通讯应用程序，我们希望通过使用主网站上的虚拟目录来隐藏我们的应用程序目录。例如，我们的应用位于 app.example.com，查看器位于 app.example.com/article/view/id。我们希望使用 example.com/newsletter/id 之类的内容作为时事通讯中的链接，供公众查看。这可能吗？如果是这样，怎么办？
这样我们就可以向读者隐藏应用程序的结构，这样人们就不会开始浏览我们应用程序的结构。是的，我们的应用程序确实有安全保障。
我相信我们使用的是 IIS 6。
For our newsletter application, we want to hide our application directory by using a virtual directory on the main website. So for instance, our app is at app.example.com and the viewer is at app.example.com/article/view/id. We would like to use something like example.com/newsletter/id as a link in the newsletter for the public to view. Is this possible? If so, how?
This is so we can hide the structure of the application from the readers so people don't start browsing the structure of our application. Yes, we do have security on the application.
I believe we are on IIS 6.
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（2）
虚拟目录只是 Web 应用程序的容器。因此，一个虚拟目录对应于一个 ASP.NET (MVC) 应用程序。它们被映射到应用程序的物理位置并属于特定的网站。当您说
app.example.com时，您已经将此域映射到 IIS 中的某个网站，因此您只能拥有子虚拟目录：app.example.com/app1,app.example.com/app2, ...但是，如果您有一个映射到example.com域的站点，那么您可以拥有对应的虚拟目录到example.com/app1、example.com/app2、... 当然，在每个应用程序中，您可以拥有与controller/action/ 相对应的路由id。Virtual directories are just containers for web applications. So a virtual directory corresponds to an ASP.NET (MVC) application. They are mapped to a physical location of the application and belong to a particular web site. When you say
app.example.comyou have already mapped this domain to some web site in IIS, so you could only have sub virtual directories:app.example.com/app1,app.example.com/app2, ... But if you have a site which is mapped to theexample.comdomain then you could have virtual directories which correspond toexample.com/app1,example.com/app2, ... And of course inside each app you could have routing which corresponds tocontroller/action/id.我们决定编写一个页面，将 html 从 myapp.domain.com 拉到domain.com/app.aspx。我们此时不想弄乱全局文件。
We decided to write a page that pulled the html from myapp.domain.com to domain.com/app.aspx. We didn't want to mess with the Global file at this time.