You can take many things for granted when you are developing for local network:
Highspeed network
Trusted user base
Same timezone for all users (this makes maintenance jobs easier to schedule among other things)
Control over which browsers and versions users should use
Authentication against LAN authentication system or no authentication at all due to trusted nature of user base
Custom port number on web-server as there is no firewall between users and web-server (though this more of deployment issue)
You will need to challenge all these assumptions when designing for extra net. For example you should estimate the slowest client connection you need to support. Oddest or most restricted browsers your users might use.
If you decide to use SSL, do check the performance of your website on the slowest connection from the beginning. I have seen many SSL sites perform terribly on slow connections.
Authentication. Who will use it externally and who will use it internally? Which parts of the site should they be able to access? So design in an authentication mechanism early to allow access based on user id and groups.
Load. Internal users may be few, but how many users will there be externally? The solution should be scalable to the number of expected users.
Will external users be guest users or must they be registered? Build a user registration component.
Whether intranet or extranet you should take sensible precautions about validating user input data before using it in your back-end SQL etc.
发布评论
评论（3）
当您为本地网络进行开发时，您可以认为许多事情是理所当然的：
高速网络
受信任的用户群
所有用户的时区相同（这使得维护工作更容易安排其他事情）
控制用户应该使用哪些浏览器和版本
针对 LAN 身份验证系统进行身份验证，或者由于用户群的可信性质而根本不进行身份验证
自定义Web 服务器上的端口号，因为用户和 Web 服务器之间没有防火墙（尽管这更多的是部署问题）
在设计额外网络时，您将需要挑战所有这些假设。
例如，您应该估计需要支持的最慢的客户端连接。 您的用户可能使用的最奇怪或最受限制的浏览器。
如果您决定使用 SSL，请从一开始就检查您网站在最慢连接上的性能。 我见过许多 SSL 站点在慢速连接上表现非常糟糕。
You can take many things for granted when you are developing for local network:
Highspeed network
Trusted user base
Same timezone for all users (this makes maintenance jobs easier to schedule among other things)
Control over which browsers and versions users should use
Authentication against LAN authentication system or no authentication at all due to trusted nature of user base
Custom port number on web-server as there is no firewall between users and web-server (though this more of deployment issue)
You will need to challenge all these assumptions when designing for extra net.
For example you should estimate the slowest client connection you need to support. Oddest or most restricted browsers your users might use.
If you decide to use SSL, do check the performance of your website on the slowest connection from the beginning. I have seen many SSL sites perform terribly on slow connections.
考虑：
您将如何进行身份验证？
不被闯入有多重要？
to consider:
How are you going to authenticate?
How important is it to not be broken into?
我会考虑一些要点。
身份验证。 谁会在外部使用它，谁会在内部使用它？ 他们应该能够访问网站的哪些部分？ 因此，请尽早设计身份验证机制，以允许基于用户 ID 和组进行访问。
加载。 内部用户可能很少，但外部用户有多少呢？ 该解决方案应该能够根据预期用户数量进行扩展。
外部用户是访客用户还是必须注册？ 构建用户注册组件。
无论是内联网还是外联网，在后端 SQL 等中使用用户输入数据之前，您都应该采取合理的预防措施来验证用户输入数据。
Some points I would consider.
Authentication. Who will use it externally and who will use it internally? Which parts of the site should they be able to access? So design in an authentication mechanism early to allow access based on user id and groups.
Load. Internal users may be few, but how many users will there be externally? The solution should be scalable to the number of expected users.
Will external users be guest users or must they be registered? Build a user registration component.
Whether intranet or extranet you should take sensible precautions about validating user input data before using it in your back-end SQL etc.