Intranet 与 Internet Web 应用程序注意事项
在设计或开发Intranet 和Internet 应用程序时考虑的因素有哪些差异？
What are the differences in considerations in respect to designing or developing an Intranet and an Internet application ?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（10）
另一件事是，在 Intranet 环境中，您通常会有一个标准的客户端构建，这意味着您可以针对特定的浏览器和应用程序进行编码。 版本（哈，通常是IE6）。
在互联网的荒野中，您必须处理各种浏览器和浏览器。 版本，所以你的 html/css/js 需要处理所有这些。
One other thing, in an intranet environment you will generally have a standard client build meaning that you can code to a specific browser & version (ha, IE6 normally).
Out in the wilds of the internet, you have to deal with all sorts of browsers & versions, so your html/css/js needs to handle all of these.
Intranet 应用程序可以利用链接到内部 UNC 路径上的资源的功能（例如
\\corporateserver\devteam\ArchitectureDiagram.vsd）。但是，请注意，浏览器处理此类链接的方式有所不同。 在 Firefox 中，默认情况下，单击 UNC 路径上资源的链接会静默失败（单击链接不会执行任何操作）； 有一些解决方法。 在 Internet Explorer 中，默认情况下，指向 UNC 路径资源的链接确实有效。
Intranet applications can take advantage of the ability to link to resources on internal UNC paths (e.g.
\\corporateserver\devteam\ArchitectureDiagram.vsd).However, be aware that browsers differ in how they handle such links. In Firefox, by default, clicking a link to a resource on a UNC path silently fails (clicking the link does nothing); some workarounds for this are available. In Internet Explorer, links to UNC path resources do work by default.
在 Intranet 上，您也许能够利用现有的身份验证和授权服务。 我工作过的银行都有非常安全的第三方身份验证服务。 在其他使用 Windows 平台的公司中，Active Directory 可用于身份验证和授权（使用“组”来定义角色）。
当这些功能可用时，您不必就散列（和加盐）或加密密码、密码强度、密码过期等做出太多决定。 而且您不必创建所有管理页面来设置用户、检索或重置密码等。用户不会在不同的 Intranet 应用程序上遇到不同的密码策略，并且通常可以对多个应用程序使用相同的登录凭据。
不必处理所有这些问题，您可以将更多时间花在应用程序的主要功能上。
尽管内联网环境似乎较少受到黑客的威胁，但只需一次破坏即可危及系统。 而且，内部网可能正在处理极其敏感的数据。 因此，我认为您需要使 Intranet 应用程序至少与 Internet 应用程序一样安全。
On an intranet, you may be able to take advantage of existing authentication and authorization services. The banks I've worked for have had very secure third-party authentication services. At other companies using Windows platforms, Active Directory can be useful for both authentication and authorization (using "groups" to define roles).
When these features are available, you don't have to make as many decisions about hashing (and salting) or encrypting passwords, password strength, password expiration, and such. And you don't have to create all the admin pages for setting up users, retrieving or resetting passwords, etc. Users are not confronted with different password policies on different intranet applications, and can often use the same login credentials for multiple applications.
Not having to deal with all of this leaves you more time to spend on the application's main features.
Even though an intranet environment may seem to be less threatened by hackers, it only takes one breach to compromise the system. And, an intranet may be dealing with extremely sensitive data. So, I think you need to make intranet applications at least as secure as Internet applications.
一些注意事项...
Some considerations...
请不要错误地认为，因为应用程序是 Intranet 专用的，所以它不需要像互联网应用程序一样安全。 如果说有什么不同的话，那就是它需要更加安全，因为它处理的数据很可能比公司互联网应用程序处理的数据更敏感。
如果您依赖 Intranet 的安全性，那么您的应用程序的安全性只能与 Intranet 一样（并且与所有用户中最弱的用户一样安全，这些用户的密码写在显示器上的便利贴上）。
Please don't make the mistake of thinking that, because an app is exclusive to the intranet, that it doesn't need to be as secure as an internet app. If anything, it needs to be more secure, as there's a good chance it will be processing data more sensitive than the data the company's internet applications process.
If you rely on the security of the intranet, then your app will only be as secure as the intranet (and as secure as the weakest of all its users, who have their passwords written on sticky notes on their monitors).
Galwegian 已经编写了其中的大部分内容，但我认为当它进入外部时你应该考虑更多的缓存，因为你的数据库可能更活跃。
另一点是，当您在企业内部（内部网）时，您可能可以使用较低的安全参数来访问用户的硬盘驱动器。 对于通过网络的外部网站/应用程序来说这是不可能的。
Galwegian have wrote most of them already but I think you should consider more caching when it goes external because your database might be more active.
An other point is when you are inside your business (intranet) you might be able to use lower security parameter to access hard drive of you user. This is not possible with external website/application via the web.
Intranet 通常有一组固定的受支持浏览器。
如果幸运的话，您可以忽略 IE6。 这很好。
Intranets often have a fixed set of browsers that are supported.
If you're lucky you can get away with ignoring IE6. Which is nice.
考虑设计考虑因素的相似之处可能会更有成效。
您仍然需要问自己同样的基本问题，例如您要解决什么问题、为谁解决问题、他们的能力是什么、您可以访问哪些平台……等等。
如果您适当考虑范围，差异很快就会变得明显。 其中许多内容已由其他贡献者在这里指出，但请尽量避免预先做出太多假设。
It might be more productive to think of the similarities in design considerations.
You still need to ask yourself the same basic questions about what you are trying to solve, for who, what are their capabilities, what platform(s) do you have access to...etc.
The differences will become apparent quickly enough if you give appropriate consideration to the scope. Many of these have been signposted by other contributors here, but try and avoid making too many assumptions up-front.
@Galwegian 和其他人：
重要的“硬”商业软件必须生存（扩展、开发）例如8-10年或更久，不间断。
@Galwegian and others:
Important "hard" business software must live, (be extended, developed) for example 8-10 years and more, without pause.
内联网应用程序更多地用于内部人员配置和知识管理目的。
其更敏感的数据可以在网络内共享
http://www.dreamznetsolutions.com/intranet_application_development_mumbai.html
Intranet Application are more for internal staffig and knowledge managemnet purposes..
its more moe sensative data to be shared within a network
http://www.dreamznetsolutions.com/intranet_application_development_mumbai.html