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