那么这样是不是就是意味着在不同的规则下面URL的形式是改变的呢?答案是不是的,大多数URL都用一个通用的格式。
大多数URL有如下的9各部分组成
<scheme>://<user>:<password>@<host>:<port>/<path>;<params>?<query>#<frag>
规则://用户:密码@主机:端口/路径;参数?查询字串#片段
上面有好多都是大家不常用的。其中最最常见的就是······规则://主机/路径······这个组合是很常见
下面我们来说一说每个组成的含义吧:
部分·············································描述·················································································默认值
scheme········································确定使用哪一种规则来取得服务器上的资源······························没有
user·············································有些规则要使用用户名来连接一个资源····································anonymous
password·····································密码在用户名的后面使用:冒号来分开·······································<emailaddress>
host············································资源的主机名字或者是IP地址··················································没有
port············································服务器上的哪一个端口在侦听,大多数规则都有默认的端口HTTP 80···特定的端口
path··········································资源在服务器上的位置用斜杠隔开·············································没有
params·····································在一些特定的规则里面使用使用参数形式是名字/值一对对出现·········没有
query·······································在一些规则里面用来传递动态参数,他和URL用?问号隔开···············没有
frag·········································资源一部分的名字。这个部分不会传送到服务器上在客户端处理·········没有
这样可能有点空泛。
下面我们来详细看下例子
URL http://tangwentao3014.ouzhe.com/resume.php这样的一个例子,HTTP是协议的名称,主机是tangwentao3014.ouzhe.com
端口没写大家都知道默认是80 路径就是/resume.php