1 |
On Wed, 16 Mar 2011 08:02:01 +0100 |
2 |
justin <jlec@g.o> wrote: |
3 |
|
4 |
> >> HOMEPAGE="http://emboss.sourceforge.net" |
5 |
> > |
6 |
> > could do with a trailing "/" |
7 |
|
8 |
I *like* to see that too... |
9 |
|
10 |
> I asked myself quite often, if this needed or not. What is the purpose |
11 |
> of the trailing "/"? |
12 |
|
13 |
However: |
14 |
|
15 |
"An HTTP URL takes the form: |
16 |
|
17 |
http://<host>:<port>/<path>?<searchpart> |
18 |
|
19 |
"where <host> and <port> are as described in Section 3.1. If :<port> |
20 |
is omitted, the port defaults to 80. No user name or password is |
21 |
allowed. <path> is an HTTP selector, and <searchpart> is a query |
22 |
string. The <path> is optional, as is the <searchpart> and its |
23 |
preceding "?". If neither <path> nor <searchpart> is present, the "/" |
24 |
may also be omitted." [1] |
25 |
|
26 |
|
27 |
|
28 |
|
29 |
|
30 |
[1] <http://www.ietf.org/rfc/rfc1738.txt>, p.8, section 3.3 |