1 |
>>>>> On Wed, 16 Mar 2011, Jeroen Roovers wrote: |
2 |
|
3 |
> "An HTTP URL takes the form: |
4 |
|
5 |
> http://<host>:<port>/<path>?<searchpart> |
6 |
|
7 |
> "where <host> and <port> are as described in Section 3.1. If :<port> |
8 |
> is omitted, the port defaults to 80. No user name or password is |
9 |
> allowed. <path> is an HTTP selector, and <searchpart> is a query |
10 |
> string. The <path> is optional, as is the <searchpart> and its |
11 |
> preceding "?". If neither <path> nor <searchpart> is present, the "/" |
12 |
> may also be omitted." [1] |
13 |
|
14 |
Right, so <http://emboss.sourceforge.net> or even |
15 |
<http://emboss.sourceforge.net:80> are legal and equivalent to |
16 |
<http://emboss.sourceforge.net/>. |
17 |
|
18 |
However, there is also a "normalized form" of URIs, which does include |
19 |
the trailing slash: |
20 |
|
21 |
"In general, a URI that uses the generic syntax for authority with |
22 |
an empty path should be normalized to a path of "/"." [2] |
23 |
|
24 |
Ulrich |
25 |
|
26 |
|
27 |
> [1] <http://www.ietf.org/rfc/rfc1738.txt>, p.8, section 3.3 |
28 |
[2] <http://tools.ietf.org/html/rfc3986#section-6.2.3> |