It doesn’t technically mean anything in particular — domains read right-to-left, so for everything to the left of a company’s domain, it’s up to the company what each bit means. (“www”, for example, is just a conventional subdomain for the web site of the company.)
I‘ve no personal experience of what www1, www2 et al are commonly used for in practice. It might well be different servers, although to my mind that’s exposing implementation details at the interface level, and is thus a bad idea.
As an example, PHP's website (at least for documentation) will forward requests to different subdomains. For example, if I go to php.net/echo, I am directed to either us2.php.net or us3.php.net. For the PHP website, it does appear that each subdomain represents a different server, but this is not necessarily the case.
这在很大程度上是推测性的，但通常每个 www'n 只是一个不同的 Web 服务器，给定的用户已被手动路由到该服务器（例如所有图像可能位于 www2 等）或通过某种形式的 up-流循环系统或负载平衡器，两者都倾向于使用最终用户 IP 地址的某些组成部分或类似的组件来确保用户的会话将保留在给定的服务器上。
顺便说一句，更现代的实现会将多个服务器的存在隐藏在单个“www”后面，以便这不那么明显/侵入。
This is largely speculative, but generally each of the www'n's is simply a different web server, which a given user has been routed to either manually (for example all images might live on www2, etc.) or by some form of up-stream round robin system or load-balancer, both of which tend to use some component of the end user's IP address or similar to ensure that a user's session will remain on a given server.
Incidentally, more modern implementations will hide the existence of multiple servers behind a single 'www', so that this is less visible/intrusive.
发布评论
评论（3）
从技术上讲，它没有任何特殊含义 - 域从右到左读取，因此对于公司域左侧的所有内容，每个位的含义取决于公司。 （例如，“www”只是公司网站的常规子域。）
我对 www1、www2 等在实践中常用的用途没有个人经验。它很可能是不同的服务器，尽管在我看来，这在接口级别暴露了实现细节，因此是一个坏主意。
It doesn’t technically mean anything in particular — domains read right-to-left, so for everything to the left of a company’s domain, it’s up to the company what each bit means. (“www”, for example, is just a conventional subdomain for the web site of the company.)
I‘ve no personal experience of what www1, www2 et al are commonly used for in practice. It might well be different servers, although to my mind that’s exposing implementation details at the interface level, and is thus a bad idea.
例如，PHP 的网站（至少对于文档而言）会将请求转发到不同的子域。例如，如果我访问 php.net/echo，我会被定向到 us2.php.net 或 us3 .php.net。对于PHP网站来说，确实看起来每个子域都代表不同的服务器，但事实并非一定如此。
As an example, PHP's website (at least for documentation) will forward requests to different subdomains. For example, if I go to php.net/echo, I am directed to either us2.php.net or us3.php.net. For the PHP website, it does appear that each subdomain represents a different server, but this is not necessarily the case.
这在很大程度上是推测性的，但通常每个 www'n 只是一个不同的 Web 服务器，给定的用户已被手动路由到该服务器（例如所有图像可能位于 www2 等）或通过某种形式的 up-流循环系统或负载平衡器，两者都倾向于使用最终用户 IP 地址的某些组成部分或类似的组件来确保用户的会话将保留在给定的服务器上。
顺便说一句，更现代的实现会将多个服务器的存在隐藏在单个“www”后面，以便这不那么明显/侵入。
This is largely speculative, but generally each of the www'n's is simply a different web server, which a given user has been routed to either manually (for example all images might live on www2, etc.) or by some form of up-stream round robin system or load-balancer, both of which tend to use some component of the end user's IP address or similar to ensure that a user's session will remain on a given server.
Incidentally, more modern implementations will hide the existence of multiple servers behind a single 'www', so that this is less visible/intrusive.